Skip to main content
Glama

dnd5e

by io.github.pipeworx-io

Get Monster

get_monster
Read-onlyIdempotent

Get monster stats including AC, HP, abilities, skills, senses, and actions. Provide monster index (e.g., "aboleth", "dragon-red-adult", "goblin"). Returns ability scores, skill bonuses, and attack/action details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesMonster index name in kebab-case (e.g. "goblin", "dragon-red-adult").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
xpYesExperience points for defeating monster
nameYesMonster name
sizeYesMonster size category
typeYesMonster creature type
indexYesMonster index identifier
speedYesMovement speeds (walk, fly, swim, etc)
hit_diceYesHit dice formula
alignmentYesMonster alignment
hit_pointsYesMaximum hit points
armor_classYesArmor class options
ability_scoresYes
challenge_ratingYesChallenge rating for encounter difficulty

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": {
+    "ability_scores": {
+      "properties": {
+        "cha": {
+          "description": "Charisma ability score",
+          "type": "integer"
+        },
+        "con": {
+          "description": "Constitution ability score",
+          "type": "integer"
+        },
+        "dex": {
+          "description": "Dexterity ability score",
+          "type": "integer"
+        },
+        "int": {
+          "description": "Intelligence ability score",
+          "type": "integer"
+        },
+        "str": {
+          "description": "Strength ability score",
+          "type": "integer"
+        },
+        "wis": {
+          "description": "Wisdom ability score",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "str",
+        "dex",
+        "con",
+        "int",
+        "wis",
+        "cha"
+      ],
+      "type": "object"
+    },
+    "alignment": {
+      "description": "Monster alignment",
+      "type": "string"
+    },
+    "armor_class": {
+      "description": "Armor class options",
+      "items": {
+        "properties": {
+          "type": {
+            "description": "AC type or source",
+            "type": "string"
+          },
+          "value": {
+            "description": "AC value",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "challenge_rating": {
+      "description": "Challenge rating for encounter difficulty",
+      "type": "number"
+    },
+    "hit_dice": {
+      "description": "Hit dice formula",
+      "type": "string"
+    },
+    "hit_points": {
+      "description": "Maximum hit points",
+      "type": "integer"
+    },
+    "index": {
+      "description": "Monster index identifier",
+      "type": "string"
+    },
+    "name": {
+      "description": "Monster name",
+      "type": "string"
+    },
+    "size": {
+      "description": "Monster size category",
+      "type": "string"
+    },
+    "speed": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Movement speeds (walk, fly, swim, etc)",
+      "type": "object"
+    },
+    "type": {
+      "description": "Monster creature type",
+      "type": "string"
+    },
+    "xp": {
+      "description": "Experience points for defeating monster",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "index",
+    "name",
+    "size",
+    "type",
+    "alignment",
+    "armor_class",
+    "hit_points",
+    "hit_dice",
+    "speed",
+    "ability_scores",
+    "challenge_rating",
+    "xp"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "index": "goblin"
+  },
+  {
+    "index": "dragon-red-adult"
+  }
+]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds details about the output (ability scores, skill bonuses, attack actions) but does not disclose extra behavioral traits like rate limits, error handling, or edge cases. No contradiction with annotations.

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

Conciseness4/5

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

The description is concise and front-loaded with the purpose. It has some redundancy between the initial stats list and the later return details, but overall it is efficient and free of fluff.

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 read-only lookup tool with a single parameter, an output schema, and comprehensive annotations, the description is sufficiently complete. It covers input and output details, though it could mention error handling or non-existence cases, which is minor.

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?

Schema coverage is 100% and the schema already describes the 'index' parameter in detail with examples. The description repeats these examples but adds no new semantic meaning beyond what the schema provides.

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 gets monster stats, listing specific attributes (AC, HP, abilities, skills, senses, actions). It distinguishes from sibling tools like get_spell and get_class by explicitly focusing on monsters and providing monster index examples.

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

Usage Guidelines4/5

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

The description gives clear usage context: it tells the agent to provide a monster index with examples. However, it does not explicitly mention when not to use this tool or name alternative tools for other entities, though the sibling context implies it.

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