Skip to main content
Glama

dnd5e

by io.github.pipeworx-io

Get Class

get_class
Read-onlyIdempotent

Get class features, hit dice, proficiencies, and advancement tables. Provide class index (e.g., "barbarian", "wizard", "rogue"). Returns feature progression, proficiency gains, and subclass options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesClass index name in lowercase (e.g. "wizard", "fighter", "cleric").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesClass name
indexYesClass index identifier
hit_dieYesHit die value (d6, d8, d10, d12)
subclassesYesAvailable subclass options
proficienciesYesProficiencies granted by class
saving_throwsYesAbility scores for saving throws

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": {
+    "hit_die": {
+      "description": "Hit die value (d6, d8, d10, d12)",
+      "type": "integer"
+    },
+    "index": {
+      "description": "Class index identifier",
+      "type": "string"
+    },
+    "name": {
+      "description": "Class name",
+      "type": "string"
+    },
+    "proficiencies": {
+      "description": "Proficiencies granted by class",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "saving_throws": {
+      "description": "Ability scores for saving throws",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "subclasses": {
+      "description": "Available subclass options",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "index",
+    "name",
+    "hit_die",
+    "saving_throws",
+    "proficiencies",
+    "subclasses"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "index": "wizard"
+  },
+  {
+    "index": "barbarian"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/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 safe read-only nature is covered. The description adds useful context by stating what the return includes ('feature progression, proficiency gains, and subclass options'), going beyond annotations without contradicting them.

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, front-loaded with the main action and resource, with no filler. Every sentence contributes to understanding what the tool does and how to use it.

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

Completeness5/5

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

The tool is simple with one parameter, an output schema exists to define returns, annotations cover safety, and the description mentions return content. Nothing critical is missing for an agent to select and invoke this tool correctly.

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 parameter 'index' is already described with examples. The description reinforces this with additional examples ('barbarian', 'wizard', 'rogue'), but this adds only marginal value beyond the schema, so a baseline of 3 is appropriate.

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 uses the specific verb 'Get' with a clear resource ('class') and enumerates what is retrieved ('features, hit dice, proficiencies, and advancement tables'). It also provides example indices, making the purpose unambiguous and distinct from sibling tools like get_monster and get_spell.

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 clearly instructs the agent to 'Provide class index' with examples, establishing when to use the tool. It does not explicitly mention alternatives or exclusions, but the sibling tools are for different entities, so the usage context is clear.

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