get_custom_taxonomyFetch a custom taxonomy by its UUID and return its full node tree, including node IDs, parent relationships, levels, positions, names, descriptions, and default status.
Get one custom taxonomy by UUID with its full node tree (each node has id, parent_id, level, position, name, description, is_default).
| Name | Required | Description | Default |
|---|---|---|---|
| taxonomy_id | Yes | Custom taxonomy UUID. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds context beyond annotations by specifying the return structure (full node tree with fields like id, parent_id, level, etc.). Annotations already indicate read-only and idempotent behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with key information, no redundant text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple retrieval tool with one parameter and no output schema, the description adequately describes the purpose and return structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter with schema coverage 100%. The description adds no extra meaning beyond the schema's description, but baseline is 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the verb 'Get' and the resource 'custom taxonomy by UUID', and distinguishes from siblings like 'list_custom_taxonomies' and 'create_custom_taxonomy'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage when needing a single taxonomy by UUID, but lacks explicit guidance on when to use vs alternatives or when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.