Skip to main content
Glama
Sign In
grandma2-mcp

grandma2-mcp

by RaSteaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ma3d_capture

Captures a uniquely identified visible local MA3D window as a PNG without UI input, so you can inspect camera and beam views. Fails for minimized, blank, or ambiguous windows.

Instructions

Save the uniquely identified visible local MA3D window as PNG, without UI input.

Windows only. Read the returned image to inspect the camera and beams. Does not start playback, select Front, or certify visual acceptance. Minimized/blank/ambiguous windows fail.

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

Input Schema

NameRequiredDescriptionDefault
window_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, non-destructive local operation; the description adds substantial value on top by disclosing failure modes (minimized/blank/ambiguous windows fail) and environment constraints (Windows only). It does not state where the PNG is written or whether repeated calls overwrite, which is why it is not a 5.

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?

Front-loaded with the core action, then constraints, then the failure modes. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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

Completeness4/5

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

No output schema exists, and the description does cover the return ('read the returned image'), but it leaves ambiguous whether an inline image or a file path is returned and where the PNG lands on disk. For a capture tool with a filesystem side effect, that is a real but modest gap.

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 0% schema description coverage, the description carries the burden and does partially: 'uniquely identified' plus 'ambiguous windows fail' explains that window_title is a disambiguator. However, the meaning of the null default (no title supplied) and what happens in that case is never explained.

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+resource: save the uniquely identified visible local MA3D window as PNG. It also scopes the operation ('without UI input', Windows only) so an agent can tell it apart from ma3d_transform and the ma2_* tooling at a glance.

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?

Explicitly sets preconditions (Windows, window must be visible and uniquely identified) and negative scope ('Does not start playback, select Front, or certify visual acceptance'), plus the follow-up action ('read the returned image to inspect the camera and beams'). It stops short of naming the sibling tool that should be used to select Front or start playback.

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