MCP Tool Discovery Taxonomist Agent
Community reusable agent prompt for classifying MCP tools into discovery taxonomies using official MCP client best practices documentation: capability grouping, naming conventions, duplicate detection, and marketplace-friendly metadata labels.
Open the source and read safety notes before installing.
Safety notes
- Taxonomy labels must not overstate tool safety—mark destructive tools explicitly.
- Duplicate detection is heuristic; human review required before merging listings.
- Renaming tools in production servers breaks client configs—coordinate version bumps.
- Classification does not replace security review of tool implementations.
Privacy notes
- Tool descriptions may embed example data with secrets—sanitize before sharing taxonomies.
- Marketplace exports should avoid attaching full JSON schemas with internal field names publicly.
- User task examples for classification should use synthetic scenarios only.
Prerequisites
- Exported tool list with names, descriptions, and input schemas from target MCP servers.
- Existing taxonomy or marketplace categories used by your organization.
- Policy on destructive versus read-only tool labeling.
- Sample user tasks showing how operators search for connectors.
Schema details
- Install type
- copy
- Troubleshooting
- No
- Scope
- Source repo
Full copyable content
## Content
MCP Tool Discovery Taxonomist Agent is a community-authored reusable prompt for organizing
MCP tool catalogs into discoverable taxonomies. It applies official MCP client best practices
documentation—not an official MCP marketplace taxonomy service.
## Scope Note
This prompt operationalizes documented client-side tool discovery and naming guidance from
modelcontextprotocol.io. Registry metadata validation is covered by mcp-registry-metadata-reviewer-agent.
## Agent Prompt
You are an MCP tool discovery taxonomist. Classify tool catalogs for operators and marketplaces
using official MCP client best practices documentation.
Workflow:
1. **Tool inventory.** Import tool names, descriptions, and schemas from each MCP server.
2. **Capability clustering.** Group tools by user intent: read, write, admin, observability, etc.
3. **Naming review.** Flag ambiguous or overlapping tool names per client best practices guidance.
4. **Duplicate detection.** Identify tools across servers with similar inputs and effects.
5. **Risk labels.** Tag destructive, data-export, or privileged tools for marketplace filters.
6. **Taxonomy proposal.** Map clusters to marketplace categories with suggested synonyms.
7. **Handoff.** Deliver taxonomy tables and rename recommendations with migration notes.
Output contract:
- Taxonomy tree with tool assignments.
- Duplicate and overlap report.
- Risk label matrix.
- Recommended metadata labels for marketplace ingestion.
## Features
- Applies MCP client best practices to tool discovery design.
- Detects overlapping capabilities across multi-server catalogs.
- Adds risk labels for marketplace filtering.
- Produces migration notes when renaming is recommended.
## Use Cases
- Organize internal MCP marketplace categories before enterprise rollout.
- Consolidate duplicate GitHub and Jira tools across multiple servers.
- Improve connector search in Claude Code host UIs.
- Prepare registry or aggregator metadata with consistent labels.
## Source Notes
Verified against MCP client best practices documentation on **2026-06-16**:
- Official client best practices documentation describes how MCP clients should present tools to
users including clarity of names, descriptions, and capability boundaries.
- Documentation emphasizes predictable tool discovery patterns so operators understand which
tool to invoke for a given task without reading full schemas.
- Client guidance complements server-side tool design docs for end-to-end discoverability.
## Duplicate Check
Checked content/agents for MCP tool taxonomy coverage.
mcp-registry-metadata-reviewer-agent validates server.json before registry publish.
No agents entry applies MCP client best practices documentation to cross-server tool taxonomy
and duplicate capability classification for marketplace discovery.
## Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public MCP client
best practices documentation. No paid placement, referral, or affiliate relationship.
## Sources
- MCP client best practices - https://modelcontextprotocol.io/docs/develop/clients/client-best-practices
- MCP tools concept - https://modelcontextprotocol.io/docs/concepts/tools
- MCP Registry about - https://modelcontextprotocol.io/registry/aboutAbout this resource
Content
MCP Tool Discovery Taxonomist Agent is a community-authored reusable prompt for organizing MCP tool catalogs into discoverable taxonomies. It applies official MCP client best practices documentation—not an official MCP marketplace taxonomy service.
Scope Note
This prompt operationalizes documented client-side tool discovery and naming guidance from modelcontextprotocol.io. Registry metadata validation is covered by mcp-registry-metadata-reviewer-agent.
Agent Prompt
You are an MCP tool discovery taxonomist. Classify tool catalogs for operators and marketplaces using official MCP client best practices documentation.
Workflow:
- Tool inventory. Import tool names, descriptions, and schemas from each MCP server.
- Capability clustering. Group tools by user intent: read, write, admin, observability, etc.
- Naming review. Flag ambiguous or overlapping tool names per client best practices guidance.
- Duplicate detection. Identify tools across servers with similar inputs and effects.
- Risk labels. Tag destructive, data-export, or privileged tools for marketplace filters.
- Taxonomy proposal. Map clusters to marketplace categories with suggested synonyms.
- Handoff. Deliver taxonomy tables and rename recommendations with migration notes.
Output contract:
- Taxonomy tree with tool assignments.
- Duplicate and overlap report.
- Risk label matrix.
- Recommended metadata labels for marketplace ingestion.
Features
- Applies MCP client best practices to tool discovery design.
- Detects overlapping capabilities across multi-server catalogs.
- Adds risk labels for marketplace filtering.
- Produces migration notes when renaming is recommended.
Use Cases
- Organize internal MCP marketplace categories before enterprise rollout.
- Consolidate duplicate GitHub and Jira tools across multiple servers.
- Improve connector search in Claude Code host UIs.
- Prepare registry or aggregator metadata with consistent labels.
Source Notes
Verified against MCP client best practices documentation on 2026-06-16:
- Official client best practices documentation describes how MCP clients should present tools to users including clarity of names, descriptions, and capability boundaries.
- Documentation emphasizes predictable tool discovery patterns so operators understand which tool to invoke for a given task without reading full schemas.
- Client guidance complements server-side tool design docs for end-to-end discoverability.
Duplicate Check
Checked content/agents for MCP tool taxonomy coverage. mcp-registry-metadata-reviewer-agent validates server.json before registry publish. No agents entry applies MCP client best practices documentation to cross-server tool taxonomy and duplicate capability classification for marketplace discovery.
Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public MCP client best practices documentation. No paid placement, referral, or affiliate relationship.
Sources
- MCP client best practices - https://modelcontextprotocol.io/docs/develop/clients/client-best-practices
- MCP tools concept - https://modelcontextprotocol.io/docs/concepts/tools
- MCP Registry about - https://modelcontextprotocol.io/registry/about
Source citations
Add this badge to your README
Show that MCP Tool Discovery Taxonomist Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/agents/mcp-tool-discovery-taxonomist-agent)How it compares
MCP Tool Discovery Taxonomist Agent side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | MCP Tool Discovery Taxonomist Agent Community reusable agent prompt for classifying MCP tools into discovery taxonomies using official MCP client best practices documentation: capability grouping, naming conventions, duplicate detection, and marketplace-friendly metadata labels. Open dossier | MCP Registry Curator Agent Community reusable agent prompt for curating MCP Registry entries for team marketplaces using official registry quickstart documentation: publish workflows, namespace ownership, version bumps, deprecations, and aggregator sync hygiene. Open dossier | Claude MCP Skills Integration Agent - Claude Code Agents MCP Skills integration specialist for remote server configuration, tool permissions, multi-MCP orchestration, and Claude Desktop ecosystem workflows. Open dossier |
|---|---|---|---|
| Trust | |||
| Install risk | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | agents | agents | agents |
| Source | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | JSONbored |
| Added | 2026-06-16 | 2026-06-16 | 2025-10-23 |
| Platforms | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — |
| Safety notes | ✓Taxonomy labels must not overstate tool safety—mark destructive tools explicitly. Duplicate detection is heuristic; human review required before merging listings. Renaming tools in production servers breaks client configs—coordinate version bumps. Classification does not replace security review of tool implementations. | ✓Publishing incorrect package pointers can redirect users to malicious artifacts—verify npm/PyPI/Docker coordinates. Deprecation without communication breaks enterprise allowlists—coordinate with platform teams. Registry curation does not replace security scanning of server code in package registries. Private servers are out of registry scope per official documentation. | ✓This agent advises connecting and using MCP servers and skills, which can run tools and commands and reach the external systems each server integrates with; review what every MCP server and skill is permitted to do before enabling it. |
| Privacy notes | ✓Tool descriptions may embed example data with secrets—sanitize before sharing taxonomies. Marketplace exports should avoid attaching full JSON schemas with internal field names publicly. User task examples for classification should use synthetic scenarios only. | ✓server.json metadata may expose internal repo URLs or staging endpoints—redact public listings. Aggregator sync logs can reveal unpublished server names—restrict access. OAuth publisher credentials for registry authentication must stay in secret stores. | ✓Connected MCP servers can read the project data you share with them and send it to the external systems they integrate with (issue trackers, databases, monitoring); review each server's data access before enabling it. |
| Prerequisites |
|
| — none listed |
| Install | — | — | — |
| Config | — | — | — |
| Citations | |||
| Claim | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.