Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_adapter_inspect_host_controls

Catalog standard Qt controls under the current Override host, including hidden controls, so you can inspect available UI elements.

Instructions

Catalog existing standard Qt controls under the current Override host, including hidden controls.

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_adapter_inspect_host_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add one genuinely useful disclosure that the result includes hidden controls, which distinguishes it from a pure visibility walk, but it says nothing about side effects, whether an Override host/session must be active, or what happens when budget_ms is exceeded.

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 no wasted words; the scope qualifier ('including hidden controls') is placed where it will be read. It is efficient, though the compactness contributes to the missing parameter and usage detail.

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?

For a tool with no annotations, no output schema, and zero schema documentation on two parameters, the definition is thin. It does not explain what a catalog entry looks like, how budget_ms bounds the traversal, or what scene_token identifies, leaving key invocation details to guesswork.

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%, so the description must compensate and does not. Neither 'scene_token' (required) nor 'budget_ms' (default 750) is mentioned, and the budget_ms time-box semantics, which likely govern how complete the catalog is, are left entirely implicit.

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 ('Catalog') and a specific resource ('standard Qt controls under the current Override host'), plus a scope qualifier ('including hidden controls'). An agent can tell this is an inspection/census tool, though it does not explicitly contrast itself with sibling inspect tools such as rest_visible_contents_inspect.

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 when-to-use, when-not-to-use, or prerequisite guidance. The agent must infer from the name that this is the tool for enumerating host Qt controls rather than, say, visible contents or simulation context, but nothing in the text routes it among the many sibling inspect tools.

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