dos2-gm-mcp

by o-shabashov

Overview Schema Source Related Servers Discussions Admin

Python

Local

List campaign backups

dos2_backups

Read-onlyIdempotent

Lists a campaign's backups newest first, providing the ID needed to restore files and undo edits.

Instructions

Lists the campaign's backups, newest first. Each entry has the id (timestamp plus operation label, e.g. "...-npc-template" or "...-full"), the label, the files that were saved, and the files that the operation created.

Read-only. Use it to find the id to pass to dos2_restore when an edit has to be undone. Returns an empty list
when the campaign has no backups yet.

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_backups"
  }
}

Input Schema

Name	Required	Description	Default
`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.

Changed1 schema field 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."

First observedv0.1.0Nov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive, so the description needn't restate safety; it adds value instead with newest-first ordering, the id's timestamp+label format, and the empty-list case. Only minor operational details (size bounds, pagination on large backup sets) are absent.

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?

Two tight paragraphs, with the scope and ordering front-loaded and the restore linkage second. The entry-contents sentence partially duplicates the output schema, but it is short and clarifies the id format in a way the schema likely does not.

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 single-parameter read with an output schema and full annotations, nothing needed to call it correctly is missing: it covers what is returned, in what order, and what an empty result means.

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?

With one parameter at 100% schema coverage, the schema already explains that campaign accepts a name, folder name, UUID, or unique fragment and points to dos2_status. The description adds no meaning about the parameter, 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?

States a specific verb and resource ("Lists the campaign's backups") plus ordering ("newest first") and enumerates what each entry contains (id, label, saved files, created files). An agent can distinguish this from dos2_restore and dos2_backup without opening a schema.

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?

Gives an explicit use case and the downstream step: find the id to pass to dos2_restore when an edit must be undone. It does not state when not to use it (e.g., a backup-creation flow), but the positive routing is concrete rather than implied.

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