grandma2-mcp

by RaSteaks

Overview Schema Source Related Servers Discussions Admin

Python

Local

ma2_connections

Read-onlyIdempotent

Connects onPC and MA3D simultaneously and returns runtime identity, Show state, and session state for each connection.

Instructions

Connect onPC and MA3D simultaneously; return runtime identity, Show and session state for each.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds that it operates on onPC and MA3D simultaneously and returns per-endpoint runtime identity, Show, and session state, but it does not clarify whether it opens persistent connections or merely inspects connection state, nor does it mention prerequisites or failure behavior.

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 filler text. It efficiently communicates the target systems and the return contents.

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 description is adequate to understand the basic operation and, because an output schema exists, it need not explain return values in detail. However, it leaves a meaningful gap around how the tool relates to ma2_status and whether 'connect' means establishing a connection or inspecting existing connection state.

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 has zero parameters, so there are no parameter semantics for the description to explain. The baseline for no parameters is 4, and the empty schema means the description does not need to compensate for undocumented inputs.

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 the action (connect/return), the resources (onPC and MA3D), the scope (simultaneously), and the returned state categories (runtime identity, Show, session state). It is specific enough for an agent to understand the tool, though it does not explicitly differentiate itself from siblings such as ma2_status.

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 explicit when-to-use guidance, no exclusions, and no named alternative such as ma2_status. The phrase 'simultaneously' clarifies scope but does not tell an agent when this tool should be selected over the other ma2/ma3d tools.

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

Deploy Server