get_vocabularyFetch a Drupal taxonomy vocabulary using its ID (vid) to inspect or manage taxonomy structure.
Get a taxonomy vocabulary by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| 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?
No annotations are provided, so the description carries the full burden. 'Get' implies a read, but it does not disclose error behavior (e.g., not-found handling), required permissions, or any return information.
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?
One short, front-loaded sentence with no wasted words. It immediately states verb, resource, and lookup key.
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 one-parameter lookup the definition is barely sufficient, but with no annotations, no output schema, and a sibling list_vocabularies, it leaves key selection and behavioral context implicit.
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?
The single required parameter 'vid' has no schema description (0% coverage), so the description's 'by ID' adds meaning by identifying vid as the vocabulary identifier. However, it does not specify the ID format or accepted value type.
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 vocabulary'), with 'by ID' scoping retrieval to a single record. It does not name list_vocabularies as the alternative, so sibling differentiation is only implicit.
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 instead of list_vocabularies or get_term, and no prerequisites or context. 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.