Skip to main content
Glama
Sign In
grandma2-mcp

grandma2-mcp

by RaSteaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ma2_backup

Saves the current grandMA2 onPC show, waits for asynchronous completion, copies a new backup, and returns its SHA256 hash to verify the backup.

Instructions

Save onPC Show, wait for asynchronous completion, copy a new backup and return SHA256. Write gate applies.

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": {
      "expected_show": "<expected_show>"
    },
    "name": "ma2_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
expected_showYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real value beyond them: the operation is asynchronous and blocks until completion, the result is a SHA256 digest, and an external 'write gate' authorization precondition applies. It stops short of saying who can satisfy the write gate or what a gate rejection looks like.

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?

A single dense sentence that front-loads the action sequence and ends with the two facts that matter operationally (return value, gate). No filler, nothing to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers the return value, and the description covers async behavior and the write gate, so those are fine. What is missing is the semantics of the one required input on a non-idempotent mutation, plus any note on where the backup is written or what a gate failure returns.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must carry it — but 'expected_show' is never explained. The phrase 'Save onPC Show' hints at a show, yet it leaves unclear whether expected_show is a show name, a path, or a verification guard asserting the currently open show. That ambiguity is the main functional gap here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb chain and resource: save the onPC Show, wait for async completion, copy a backup, return its SHA256. That is far more precise than the name alone. It does not, however, distinguish itself from siblings like ma2_export or ma2_execute, which an agent must guess between.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this versus ma2_export (also an export-flavored sibling) or how it relates to ma2_list/ma2_status. 'Write gate applies' signals a precondition exists but never says what triggers it or what happens when it fails. The agent gets no routing guidance.

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