Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_dock_identity_inspect

Inspect dock identity properties by reading fixed candidates, including hidden identities, ancestor docks/stacks, and action associations. Verify scene structure without traversal or simulation.

Instructions

Read fixed property candidates including hidden identities, ancestor docks/stacks and action associations.

No hidden numeric traversal, action/slot/toggle, simulation, logger changes or panel creation.

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

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenYes

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 still conveys that this is a read-only inspection and explicitly rules out several side effects or action-related behaviors. It does not describe return shape, error conditions, permissions, or how budget_ms affects behavior, leaving meaningful 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?

The description is short and front-loaded, with the core read purpose in the first sentence and boundary exclusions in the second. It is efficient, though the dense domain jargon slightly reduces immediate clarity.

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 output schema, no annotations, and no schema parameter descriptions, the definition is incomplete. It explains what categories are read and what is avoided, but omits return information and parameter meaning that an agent would need to invoke it confidently.

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, but it does not mention either scene_token or budget_ms. The parameter names are somewhat inferable, but their semantics, especially budget_ms, are left unstated.

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?

The description names a specific read operation over dock identity-related data: fixed property candidates, hidden identities, ancestor docks/stacks, and action associations. This is more specific than a tautological restatement, though the phrase 'fixed property candidates' remains somewhat opaque.

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?

The second sentence usefully lists operations this tool does not perform, which implicitly helps an agent avoid using it for numeric traversal, actions/toggles, simulation changes, logging, or panel creation. However, it gives no explicit positive guidance on when to choose this tool over 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