Skip to main content
Glama

dnd5e

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate idempotent, non-read-only, non-destructive. The description adds valuable context: storage as key-value pairs scoped by user identifier, persistence for authenticated users, and 24-hour retention for anonymous sessions. This goes beyond annotations to explain lifecycle and scoping.

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 concise and front-loaded, starting with the core purpose, then usage, then storage details. Each sentence contributes meaningful information, and no word is wasted.

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?

For a simple two-parameter tool with no output schema, the description covers all essential aspects: purpose, when to use, persistence behavior, scoping, and companion tools. It is fully sufficient for an agent to invoke it 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 both parameters (key, value) are well-described with examples in the schema. The description does not add additional meaning beyond what the schema provides, making a baseline score of 3 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 clearly states the tool saves data for reuse, using the verb 'save' and specifying the resource as key-value pairs. It also distinguishes itself from sibling tools by explicitly naming recall and forget for retrieval and deletion.

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?

Provides clear 'when to use' guidance with examples (resolved ticker, target address, etc.) and mentions pairing with recall/forget as alternatives. It does not explicitly state 'when not to use', but the context is sufficient for an agent to decide.

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