Fetch D&D 5e spell information by name or index to look up casting rules and details during gameplay or agent tasks.
Get a D&D 5e spell by name/index.
| Name | Required | Description | Default |
|---|---|---|---|
| spell | Yes | Spell index (e.g. 'fireball', 'magic-missile') |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds little behavioral context beyond the lookup action and does not mention not-found behavior or return details.
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 wasted words. It communicates the action and identifier immediately.
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 with full schema coverage and rich annotations, the description is sufficient for correct invocation. It could mention the spell object returned, but the tool's complexity is low enough that this is a minor gap.
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 100% and the single 'spell' parameter already includes an example format. The description only restates that lookup is by name/index, so baseline 3 is appropriate.
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 and resource: get a D&D 5e spell by name/index. It is clearly distinct from listing tools like dnd_list_spells, though it does not explicitly name that sibling.
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?
The phrase 'by name/index' implies usage when the caller already has an identifier, but the description gives no explicit when-to-use guidance or alternative such as dnd_list_spells for discovery.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.