Skip to main content
Glama
Sign In
grandma2-mcp

grandma2-mcp

by RaSteaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ma3d_transform

Destructive

Set x/y/z and rotation values or camera FOV for an inspected scene Root or camera, then return before/after List changes for MA3D or onPC synchronization.

Instructions

Set x/y/z (metres), rx/ry/rz (degrees), or camera fov (radians), and return before/after List.

Requires an inspected scene Root address or Camera number. Installation orientation is NOT programmed Pan/Tilt. MA3D edits can synchronize into onPC. Use target=onpc if its shared scene is the intended authority. Requires write gate and expected Show; no visual pass is implied.

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>",
      "expected_show": "<expected_show>",
      "values": "<values>"
    },
    "name": "ma3d_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYes
targetNoma3d
valuesYes
expected_showYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructive/non-idempotent annotations, the description discloses synchronization into onPC, the write-gate and expected-Show requirements, and the important caveat that installation orientation is not programmed Pan/Tilt. It also clarifies that edits may propagate externally and that no visual validation is implied.

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 core operation is front-loaded in the first sentence, and the remaining sentences carry prerequisites, synchronization behavior, and safety caveats without padding. Every sentence earns its place.

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?

The tool is complex and destructive, with no schema descriptions, but the description supplies the missing parameter semantics, prerequisites, target guidance, and side-effect context. Since an output schema exists, it does not need to explain the before/after List return structure in detail.

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?

With 0% schema description coverage, the description adds substantial meaning for object, target, values, and expected_show: it explains accepted transforms and units, the Root-address/Camera-number requirement, and target=onpc. It stops short of fully documenting the values map contract or exact expected_show format, so a small gap remains.

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?

The description names a specific verb and resource: setting x/y/z, rx/ry/rz, or camera fov on a MA3D object. It also distinguishes the onPC target case and return value, so the agent can tell what this tool does without inspecting siblings in depth.

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

Usage Guidelines5/5

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

It gives clear prerequisites (inspected scene Root address or Camera number, write gate, expected Show) and an explicit alternative path: use target=onpc when the shared onPC scene is the intended authority. It also rules out assuming a visual pass.

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