Skip to main content
Glama

dnd5e

by io.github.pipeworx-io

Get Spell

get_spell
Read-onlyIdempotent

Get spell details including damage, range, duration, components, and effects. Provide spell index (e.g., "fireball", "magic-missile", "cure-wounds"). Returns damage dice, range, casting time, and effect descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesSpell index name in kebab-case (e.g. "fireball", "magic-missile").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSpell name
indexYesSpell index identifier
levelYesSpell level (0-9)
rangeYesSpell range
ritualYesWhether spell can be cast as ritual
schoolYesSchool of magic
classesYesClasses that can cast this spell
durationYesSpell duration
materialNoMaterial components required
componentsYesSpell components (V, S, M)
descriptionYesSpell effect descriptions
casting_timeYesTime required to cast spell
higher_levelNoEffects at higher spell levels
concentrationYesWhether spell requires concentration

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "casting_time": {
+      "description": "Time required to cast spell",
+      "type": "string"
+    },
+    "classes": {
+      "description": "Classes that can cast this spell",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "components": {
+      "description": "Spell components (V, S, M)",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "concentration": {
+      "description": "Whether spell requires concentration",
+      "type": "boolean"
+    },
+    "description": {
+      "description": "Spell effect descriptions",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "duration": {
+      "description": "Spell duration",
+      "type": "string"
+    },
+    "higher_level": {
+      "description": "Effects at higher spell levels",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "index": {
+      "description": "Spell index identifier",
+      "type": "string"
+    },
+    "level": {
+      "description": "Spell level (0-9)",
+      "type": "integer"
+    },
+    "material": {
+      "description": "Material components required",
+      "type": "string"
+    },
+    "name": {
+      "description": "Spell name",
+      "type": "string"
+    },
+    "range": {
+      "description": "Spell range",
+      "type": "string"
+    },
+    "ritual": {
+      "description": "Whether spell can be cast as ritual",
+      "type": "boolean"
+    },
+    "school": {
+      "description": "School of magic",
+      "type": "string"
+    }
+  },
+  "required": [
+    "index",
+    "name",
+    "level",
+    "school",
+    "casting_time",
+    "range",
+    "duration",
+    "concentration",
+    "ritual",
+    "components",
+    "description",
+    "classes"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "index": "fireball"
+  },
+  {
+    "index": "magic-missile"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it 'Returns damage dice, range, casting time, and effect descriptions,' which is helpful but largely redundant given the output schema exists. No additional behavioral traits such as permission requirements or edge cases are disclosed, so the description adds only marginal transparency beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and immediately front-loads the purpose ('Get spell details'). It includes necessary examples and a brief return summary without any wasted words. Every sentence serves a clear function, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter tool with an output schema and strong annotations, the description is largely complete. It states the input requirement, gives examples, and outlines what information is returned. The only gap is the lack of explicit guidance on using list_spells for browsing or finding indices, but this is a minor omission given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage with a detailed description of the 'index' parameter including kebab-case examples. The description repeats 'Provide spell index' and offers the same examples from the schema, adding no new semantic information. Since the schema already documents the parameter fully, the description's contribution is minimal, warranting the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Get') and resource ('spell details'), and lists the types of information returned (damage, range, duration, components, effects). It also provides concrete examples of valid indices, leaving no ambiguity about what the tool does. The sibling tool list includes list_spells, which reinforces the distinct lookup-by-index purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a prerequisite by instructing the user to 'Provide spell index' and gives example indices, which implies the tool is used when you already know the specific spell. However, it does not explicitly mention when to use this over sibling tools like list_spells or get_monster, nor does it state any exclusions. Usage context is implied but not fully articulated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dnd5e toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as the three ask_pipeworx variants, the memory tools (remember/recall/forget), and the subscription management tools. Additionally, the D&D tools are mixed with a large set of unrelated tools, causing confusion between domains.

Naming Consistency2/5

Naming conventions are inconsistent: some tools follow verb_noun pattern (e.g., get_class, list_spells), while others use descriptive noun phrases (e.g., ai_visibility_check, polymarket_arbitrage). There is no clear, predictable pattern across the set.

Tool Count2/5

With 35 tools, the count is high for a server ostensibly focused on D&D 5e. The inclusion of many unrelated tools from the Pipeworx ecosystem makes the set feel bloated and unfocused for the intended domain.

Completeness1/5

For the D&D 5e domain, only 4 tools exist (get_class, get_monster, get_spell, list_spells), which is severely incomplete. The remaining tools cover other domains, but they do not serve the server's primary purpose, leaving obvious gaps in functionality.

Resources