Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_probe_runtime

Reads adapter configuration and blocked status without loading DLLs or calling the MD API, so you can verify runtime readiness before scene operations.

Instructions

Read adapter configuration/blocked status. No DLL loading or MD API call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 one important trait: no DLL loading and no MD API call, implying a safe, side-effect-free read. It does not say whether the probe can fail, whether it requires a loaded host, or what it returns, so transparency is partial.

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?

Two short sentences, action stated first and the side-effect caveat second, with no filler. The only weakness is that the second sentence is terse enough to be cryptic about what "DLL loading" means in context.

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

Completeness3/5

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

For a zero-parameter diagnostic tool with no output schema, the description should convey what the returned "configuration/blocked status" looks like, but it does not. It is adequate to identify the operation but leaves the agent guessing at the result shape.

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?

The tool takes zero parameters and the schema is an empty object, so there are no parameter semantics to explain; the baseline for a parameterless tool applies. The description correctly adds no redundant parameter prose.

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 pairs a specific verb ("Read") with a resource ("adapter configuration/blocked status"), which is more than a restatement of the name. However, "adapter" is left undefined — it is unclear whether this is the world/scene adapter or a generic one, and nothing distinguishes it from adjacent probes such as cloth_probe_runtime, mesh_probe_runtime, or world_adapter_inspect_3d.

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 the many sibling inspect/probe/runtime_capabilities tools. The second sentence is a negative side-effect claim rather than a usage condition, so an agent gets no routing guidance.

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