Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_gizmo_scale_inspect

Read the two fixed Gizmo Scale actions in the current view without triggering them, so you can verify available scale options before activation.

Instructions

Read the two fixed Gizmo Scale actions in the current view without triggering them.

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

Input Schema

NameRequiredDescriptionDefault
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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: the read does not trigger the actions, i.e. it is side-effect free. Beyond that it is silent on whether the current view must be active, what happens if the actions are missing, and what the read returns, which are real gaps for an unannotated tool.

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?

It is one tight, front-loaded sentence with no filler, and the key constraint (non-triggering) lands at the end of a short clause. The terseness costs clarity, but there is no wasted wording to cut.

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?

There is no output schema, no annotations, and no documented parameter, yet the description never says what a successful read produces (presumably the two action definitions) or what failure looks like. For an inspection tool whose entire value is the returned data, that is a substantial omission.

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% and the single required parameter, scene_token, is never mentioned in the description. The agent must infer that the token identifies "the current view" referenced in the text, and nothing is said about format, sourcing, or whether the token scopes the read.

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 gives a concrete verb ("Read") and a named resource ("the two fixed Gizmo Scale actions in the current view"), so the agent knows it is an inspection tool. However, "the two fixed Gizmo Scale actions" is unexplained domain jargon, and the phrase does not clarify what an "action" actually is or what gets read back, leaving the purpose only partially pinned down.

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?

"without triggering them" implies the usage discriminator: use this when you want to look at the scale actions rather than execute or prove them, which implicitly separates it from siblings like world_gizmo_scale_prove_roundtrip and world_gizmo_scale_recover_pair. No alternative is named explicitly and no preconditions are stated, so the guidance remains implied rather than stated.

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