Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Yamazaki Tower Three-Tier Display Tray

tds_purchase_a24
Read-onlyIdempotent

Recorded model Tower Three-Tier Display Tray. Use the seller’s model field or exact variant name. Use one upright layer of rectangular footprints. Check weight, height and stability separately.

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>",
      "usableWidthCm": "<usableWidthCm>",
      "usableDepthCm": "<usableDepthCm>",
      "footprintWidthCm": "<footprintWidthCm>",
      "footprintDepthCm": "<footprintDepthCm>",
      "gapCm": "<gapCm>"
    },
    "name": "tds_purchase_a24"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds a small processing constraint (evaluate one upright layer of rectangular footprints; check weight, height and stability separately) but does not say what the tool returns, whether anything is persisted, or why the call is read-only despite the 'purchase' name. No contradiction with annotations, but thin added context.

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?

Four short sentences with no filler, which is appropriately sized. But the lead sentence is malformed ("Recorded model …") and the closing sentence about weight, height and stability refers to concerns that have no corresponding inputs, so it reads as leftover context rather than actionable guidance.

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?

A six-required-parameter tool with zero schema description coverage, no output schema and a cryptic tool name needs substantially more explanation than this. Missing are units/semantics for gapCm, the meaning of usable vs footprint dimensions, and what the call actually produces or records — an agent must guess on several required inputs.

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 all six parameters are required, so the description must carry the meaning. It explains offeredModel (seller's model field or exact variant name) and partially explains footprintWidthCm/footprintDepthCm via 'rectangular footprints'. It never mentions gapCm, and usableWidthCm/usableDepthCm are only implied by the word 'usable'. It also tells the agent to check weight, height and stability, but no such parameters exist, which muddies rather than clarifies.

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 names a concrete product (Yamazaki Tower Three-Tier Display Tray) and the description ties the tool to that product, distinguishing it from other tds_purchase_* siblings by product identity. However, the operative verb is garbled — "Recorded model Tower Three-Tier Display Tray" never states whether this records a purchase, computes a fit plan, or stores dimensions. An agent can tell which product it applies to but not what action it performs.

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?

It gives real procedural guidance — "Use the seller's model field or exact variant name" and "Use one upright layer of rectangular footprints" — which tells the agent how to fill in inputs. It gives no guidance on when to choose this tool versus the many other product-specific siblings, and no prerequisites or exclusions.

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.