dos2-gm-mcp

Overview Schema Source Related Servers Discussions Admin

List saved templates

dos2_templates

Read-onlyIdempotent

Lists a campaign's saved Game Master NPC and item templates as short summaries, optionally filtered by kind, to inspect available templates before fetching full details.

Instructions

Lists the campaign's saved Game Master templates (the "Creatures and Items" panel, stored in Eggs.lsf) as short summaries. NPC entries have name, stat_name, template_id, level, alignment, skills and item stats ids; item entries have name, stats_id, template_id and level.

Read-only. Use dos2_template to get one template in full, and dos2_find_templates to search by substring across
all campaigns, including Larian's sample ones.

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": "dos2_templates"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Filter by kind: "npc" or "item". Omit to list both.
`campaign`	Yes	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.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Nov 11, 2026

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 / kind / description

Added value: +"Filter by kind: \"npc\" or \"item\". Omit to list both."

First observedv0.1.0Nov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's "Read-only" merely restates it. It does add value with the storage location and the per-kind shape of each entry (NPC vs item fields), giving the agent a preview of what a listing actually contains.

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?

Three sentences, front-loaded with what the tool returns, followed by behavior and alternatives. Slight waste in repeating "Read-only" already covered by annotations, and the field lists are the kind of detail an output schema usually carries.

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 two-parameter, read-only list tool with a full schema and an output schema, this is nearly complete: purpose, scoping, sibling routing and result shape are all present. The only gap is minor redundancy in re-describing return fields that the output schema already defines.

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 documents both the kind filter ("npc"/"item", omit for both) and campaign resolution. The description adds nothing about parameters beyond that, so the baseline 3 applies; the field enumeration it does provide concerns return values, not inputs.

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?

Names a specific verb and resource: lists the campaign's saved Game Master templates, and pins down scope by identifying the source panel/file ("Creatures and Items" panel, Eggs.lsf) and the summary-level nature of the output. It also enumerates the returned fields per kind, which lets an agent distinguish this list view from a full template fetch.

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 routes the agent: use dos2_template for a single full template and dos2_find_templates to search by substring across all campaigns including Larian's samples. Both the alternative and the condition that selects it are stated, so no inference is required.

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