dos2-gm-mcp

Overview Schema Source Related Servers Discussions Admin

Server status and campaign list

dos2_status

Read-onlyIdempotent

Reports server setup and lists available GM campaigns with paths, backups, and game process status so you can choose a campaign and verify readiness before editing or running it.

Instructions

Reports the server's setup and lists the GM campaigns. Returns the campaigns folder, the path to Divine.exe and whether it exists, the backups folder, whether the game process is running, and for every campaign its name, folder, UUID, add-ons, scene count and last-modified time.

Read-only, no parameters. Call it first in a session to choose a campaign and check setup: if divine_found is
false, run dos2_fetch_lslib before any other tool. For the readiness of the running game (Script Extender,
bridge mod) use dos2_live_status instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dos2_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Although annotations already declare readOnlyHint, idempotentHint and destructiveHint, the description adds information annotations cannot carry: the full set of returned fields (necessary here since there is no output schema) and a prerequisite rule keyed on the returned divine_found value. That prerequisite branch is a behavioral trait, not a restatement of annotations, and it changes what the agent does next.

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?

Two short paragraphs: the first states what is returned, the second states when to call it and what to do based on the result. It is front-loaded with the action and contains no filler or redundant restatement of the title.

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 parameterless read-only status tool with no output schema, the description covers the gap by listing the return fields and explaining the one decision the tool drives (campaign selection and the divine_found branch). Nothing an agent needs in order to call it correctly or act on its result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters and the description says so plainly ('no parameters'), which is consistent with the empty schema. With zero parameters there is nothing further to disambiguate, so the baseline applies.

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 names a specific verb and resource ('Reports the server's setup and lists the GM campaigns') and then enumerates the exact fields returned, including the per-campaign fields name, folder, UUID, add-ons, scene count and last-modified time. It also distinguishes itself from the sibling dos2_live_status, which handles running-game readiness, so an agent can tell the two apart without opening either schema.

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?

It gives explicit placement ('Call it first in a session'), the purpose of that placement ('choose a campaign and check setup'), and a concrete conditional branch ('if divine_found is false, run dos2_fetch_lslib before any other tool'). It also routes the adjacent case away to a named sibling: 'For the readiness of the running game ... use dos2_live_status instead.'

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