Skip to main content
Glama

The Doll Scout Home Tools

Check bathroom mounting clearance · Yamazaki Table Mirror

tds_purchase_m_yamazaki_standing_mirror
Read-onlyIdempotent

Recorded model Table Mirror. Use the seller’s model field or exact variant name. Use measurements for the exact variant, including required clearances.

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": {
      "offeredModel": "<offeredModel>",
      "availableWidthCm": "<availableWidthCm>",
      "availableHeightCm": "<availableHeightCm>",
      "mountedWidthCm": "<mountedWidthCm>",
      "mountedHeightCm": "<mountedHeightCm>",
      "serviceMarginCm": "<serviceMarginCm>"
    },
    "name": "tds_purchase_m_yamazaki_standing_mirror"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
mountedWidthCmYes
mountedHeightCmYes
serviceMarginCmYes
availableWidthCmYes
availableHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds that the check depends on the exact variant and required clearances, but it does not explain the result format, validation behavior, or what happens when the model or measurements do not match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the first sentence is a cryptic fragment and the input guidance is not front-loaded or organized around the tool's operation. It avoids bloat, but the brevity is coupled with under-specification rather than crisp structure.

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 six-parameter clearance-check tool with no output schema, the description is too thin. It provides partial input guidance but does not state what the tool returns, how success or failure is represented, or how the measurement parameters combine to produce a clearance result.

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 six required parameters, so the description must carry the burden. It only vaguely maps to offeredModel and to measurements/clearances; it does not explain the distinctions between available versus mounted dimensions, what serviceMarginCm represents, or how the clearance check uses these values.

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 title indicates a bathroom mounting clearance check for a Yamazaki Table Mirror, but the description itself opens with the fragment 'Recorded model Table Mirror' and never states a clear verb or what result is produced. It implies a variant-specific clearance check through 'Use measurements ... including required clearances,' but the purpose is only indirectly conveyed.

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?

The description tells the agent to use the seller's model field or exact variant name and to use measurements for the exact variant, which is input guidance rather than when-to-use guidance. It gives no explicit conditions for using this tool, no exclusions, and no alternatives among the many sibling product tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.