get_termRetrieve a taxonomy term by its vocabulary ID and term ID. Use it to fetch term details from a Drupal site for content tagging or categorization.
Get a taxonomy term by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| tid | Yes | ||
| vid | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It does not state what happens when the term is missing, whether it is a pure read, whether unpublished/hidden terms are returned, or any access requirements beyond the implied 'Get'.
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?
A single front-loaded sentence with no filler. It is efficient, though its brevity is partly due to under-specification rather than discipline.
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?
An output schema exists, so return values need not be described, and the tool is simple with only two parameters. However, the unexplained 'vid' parameter and total absence of fallback/usage context leave a real gap for an agent trying to invoke it correctly.
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?
Schema coverage is 0% and the description only explains one of two parameters implicitly ('by ID' maps to tid). The required 'vid' vocabulary identifier is never explained, so the agent gets no help understanding how to supply it.
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?
States a specific verb (Get) and resource (taxonomy term) with an identifying key (by ID). It does not differentiate itself from the many sibling getters (get_node, get_user, get_vocabulary), but the resource is unambiguous.
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?
No guidance on when to use this versus list_terms, create_term, or get_vocabulary, and no prerequisites or lookup-by-other-field alternative mentioned. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.