Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_simulation_context_inspect

Reads fixed SimStop, Drape, and Brush actions, buttons, meta declarations, and SDK docs to inspect simulation context without triggering actions or changing solver state.

Instructions

Read fixed SimStop/Drape/Brush actions, their associated buttons, real meta declarations and fixed SDK docs.

Does not trigger actions, invoke slots or SDK getters, start/stop simulation or create dialogs. QAction checked states remain observations; they are not independently verified solver running state.

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

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does useful work: it declares a non-mutating read profile and adds a real caveat that QAction checked states are observations, not verified solver running state. However, it omits other behavior an agent needs, such as response size, whether the read can be slow, and what 'budget_ms' controls in practice.

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?

Three short sentences, front-loaded with the resource list and followed by the constraints. No filler, though the dense slash-separated jargon ('SimStop/Drape/Brush', 'real meta declarations') costs some readability.

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?

The description roughly characterizes the return content (actions, buttons, meta, SDK docs), which partly offsets the missing output schema, and it clearly establishes the no-side-effects contract. It remains incomplete on parameter meaning and on the size/cost of the returned context for a tool that takes an explicit time budget.

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, so the description must compensate and does not: scene_token and budget_ms are never mentioned. 'budget_ms' in particular is opaque (a timeout? a target latency?) and the description gives no hint about how much context is returned per budget.

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?

States a specific verb ('Read') and enumerates the resources returned: fixed SimStop/Drape/Brush actions, associated buttons, meta declarations and SDK docs. The term 'fixed' is undefined jargon, which blurs the boundary slightly, but an agent can still tell this is a static metadata/inspection read rather than an execution tool.

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

Usage Guidelines3/5

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

Usage is implied mainly through exclusions: it does not trigger actions, invoke slots or SDK getters, start/stop simulation or create dialogs, which tells the agent to use it for passive inspection rather than control. No sibling tool is named and there is no explicit 'use this when...' condition, so the agent must infer the routing itself.

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