Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

mesh_probe_runtime

Reads fixed OBJ API and option metadata for a scene, helping inspect settings without exporting or modifying the model.

Instructions

Read fixed OBJ API/option metadata; performs no export or model modification.

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

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo

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, the description carries the full burden, and it does disclose a genuinely useful negative capability: no export and no model modification. Beyond that it says nothing about permissions, whether the metadata is cached or live, or what the probe returns, which is thin for a tool with zero annotation coverage.

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?

One compact sentence with no filler, and the read-only framing is front-loaded. The economy is slightly undermined by opaque jargon rather than verbosity.

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, no output schema, an unexplained parameter, and an ambiguous resource mean the definition leaves the agent guessing about both inputs and return shape. More is required for a tool whose entire contract rests on the description.

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?

There is a single parameter, scene_token, with 0% schema description coverage, and the description never mentions it. Since coverage is low, the description should explain what the token selects and whether null means current scene, but it offers no guidance at all.

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 operation on 'fixed OBJ API/option metadata', which suggests a runtime inspection tool, but 'fixed' and 'API/option metadata' are jargon that leave the actual resource ambiguous. It does not explicitly distinguish itself from the many sibling *_probe_runtime tools, so the agent must infer domain from the name prefix alone.

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 statement of when to call this versus mesh_read_scene, mesh_read_group, mesh_read_pattern, or the other probe tools. The only usable cue is the implied read-only inspection context, which must be derived rather than 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