Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_numeric_probe_inspect

Reads existing Translate 3D instances, including hidden ones, plus their Qt numeric controls and method declarations so you can inspect scene values and available methods.

Instructions

Read existing Translate 3D instances, including hidden ones, and their Qt numeric controls and method declarations.

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": {
      "scene_token": "<scene_token>"
    },
    "name": "world_numeric_probe_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses that hidden instances are included, but it says nothing about whether the tool is read-only (only implied), what budget_ms controls, whether it mutates state, permission needs, or what the response contains. For a probe-style tool this leaves significant behavioral gaps.

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

Conciseness4/5

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

A single front-loaded sentence with little filler. The jargon ('Qt numeric controls', 'method declarations') is dense but every phrase carries content; no wasted sentences.

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?

No annotations and no output schema, so the description must explain behavior and return shape. It fails to cover the undocumented budget_ms parameter, return format, or the safety profile, which is too thin for a diagnostic tool with two parameters.

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% for both parameters. The description does not explain scene_token's format/expectations or what the 500ms budget_ms time budget means and whether exceeding it truncates results. It adds virtually no meaning beyond the raw schema.

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?

Names a specific verb ('Read') and a specific resource ('existing Translate 3D instances ... and their Qt numeric controls and method declarations'). The scope ('including hidden ones') is concrete. It does not distinguish itself from inspection siblings like world_adapter_inspect_3d or cut_qt_inspect, so it stops short of a 5.

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 guidance on when to choose this over the many other inspect/probe tools, no prerequisites, and no statement of when not to use it. The 'inspect' framing only implies a diagnostic read.

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