Skip to main content
Glama
Sign In
grandma2-mcp

grandma2-mcp

by RaSteaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ma2_export

Export a local grandMA2 object to unique XML and return a timestamp-independent fingerprint for reliable change tracking and comparison.

Instructions

Export a local native object to unique XML and return a timestamp-independent fingerprint.

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": {
      "object": "<object>"
    },
    "name": "ma2_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYes
targetNoonpc

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare that the tool is non-read-only, non-idempotent, non-destructive, and closed-world. The description adds useful behavioral context by stating that the output is unique XML and a timestamp-independent fingerprint, but it does not disclose where the XML is written or what side effects the export has.

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?

The description is a single front-loaded sentence with no redundant or filler content. It communicates the action and the distinctive return artifact efficiently.

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?

An output schema exists, so return-value details do not need to be repeated, and annotations cover the safety profile. However, the 0% parameter coverage and lack of usage guidance leave meaningful gaps for an agent deciding how to call the tool correctly.

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%, so the description must explain the parameters, but it does not. The required 'object' parameter is only vaguely implied by 'local native object', and the 'target' parameter with default 'onpc' is entirely unaddressed.

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 gives a specific verb and resource: it exports a local native object to XML and returns a fingerprint. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as ma2_backup.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention ma2_backup, ma2_list, or any conditions or exclusions for selecting ma2_export.

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