Skip to main content
Glama
Sign In
dos2-gm-mcp

dos2-gm-mcp

by o-shabashov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get one template in full

dos2_template
Read-onlyIdempotent

Reads one saved Game Master template in full, including NPC stats, edits, abilities, skills and items, so you can inspect it before editing.

Instructions

Returns one saved Game Master template of the campaign in full: for an NPC its base stats, the GM's stat edits, abilities, talents, skills, skill bar and items with slots; for an item all of its attributes.

Read-only. Fails with an error when the campaign has no template with that name. Use it to inspect a template
before changing it with dos2_put_npc_template or dos2_put_item_template. To list the available names use
dos2_templates; to search across campaigns use dos2_find_templates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign": "<campaign>",
      "name": "<name>"
    },
    "name": "dos2_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact template name (case-insensitive), as listed by dos2_templates.
campaignYesThe campaign to work on: its name, its folder name, its UUID, or a unique part of any of them. dos2_status lists the campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / campaign / description
      Added value: +"The campaign to work on: its name, its folder name, its UUID, or a unique part of any of them. dos2_status lists the campaigns."
    • addedInput schema / properties / name / description
      Added value: +"Exact template name (case-insensitive), as listed by dos2_templates."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered structurally; the description still adds value by stating 'Read-only' and disclosing the failure mode ('Fails with an error when the campaign has no template with that name'). It does not describe pagination, size limits, or response envelope, but for a single-record read the disclosure is adequate.

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?

Front-loads the core action and return scope, then terse lines for read-only behavior, error condition, and sibling routing. Every sentence carries distinct information with no restating of the title or name.

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?

With no output schema, the description compensates by summarizing exactly what is returned for each template kind, plus the error case and the recommended follow-up tools. An agent has everything needed to call this correctly and interpret the result.

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 ('campaign', 'name') are already documented in the schema with case-insensitivity and accepted identifier forms. The description adds no syntax or format detail beyond what the schema provides, so the baseline 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?

States a specific verb and resource ('Returns one saved Game Master template of the campaign in full') and even enumerates what full means for the two template kinds (NPC base stats, edits, abilities, talents, skills, skill bar, items vs. item attributes). This clearly separates it from list/search/put siblings without requiring the schema to be opened.

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

Usage Guidelines5/5

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

Explicitly states the when-to-use case ('inspect a template before changing it with dos2_put_npc_template or dos2_put_item_template') and routes the agent to named alternatives for other needs ('dos2_templates' to list names, 'dos2_find_templates' to search across campaigns). No inference is left to the agent.

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

Deploy Server

Other Tools