Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_transform_probe

Reads actual transform symbols and docs, plus an optional current UUID index, to inspect scene transform data without applying setters or saving projects.

Instructions

Read actual transform symbols/docs and optional current UUID index.

Does not call a setter, load/save a project, or infer a world contract from symbol presence. The default native world writer is unavailable.

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

Input Schema

NameRequiredDescriptionDefault
pattern_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose meaningful boundaries: it does not mutate via a setter, does not load or save a project, and does not derive a world contract from symbol presence. The note that "the default native world writer is unavailable" is a genuinely useful environmental caveat. However, nothing is said about what the probe returns, whether it can fail, or what the caller should do with the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the read action, which is good. But roughly two-thirds of the text is spent on negative disclaimers, and the word "actual" in the opening clause adds no discriminating information. Space that could have described the output was spent on exclusions instead.

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

Completeness2/5

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

There is no output schema and no annotations, so the description is the only source of truth for a tool whose name suggests returning symbol/document data. It never characterizes the return value or the shape of "symbols/docs," leaving an agent unable to predict what a successful call yields. For a probe tool that is defined entirely by its output, this is a substantive 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?

Schema description coverage is 0% for the single optional pattern_uuid parameter, so the description must compensate. The phrase "optional current UUID index" at least confirms the parameter is optional and is a UUID index, adding some meaning beyond the bare anyOf string/null type. It stops short of explaining what index means, what happens when it is omitted, or what a UUID identifies.

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

Purpose3/5

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

The description names a read verb and a resource ("Read actual transform symbols/docs and optional current UUID index"), so it is clearly an inspection tool. But "transform symbols/docs" is domain jargon that never resolves into what is actually retrieved, and nothing distinguishes it from sibling probes such as world_numeric_probe_inspect or md_capabilities. An agent knows it is a probe, not what it probes for.

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 guidance is entirely negative: no setter call, no project load/save, no world-contract inference. These exclusions imply a safe read-only inspection role, but the description never says when to reach for this tool or which sibling probe to use instead. No positive usage condition is stated.

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