Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Wood-Top Slipper Rack

tds_purchase_m_yamazaki_wood_top_slipper_rack
Read-onlyIdempotent

Recorded model Wood-Top Slipper Rack. 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>",
      "itemWidthCm": "<itemWidthCm>",
      "itemDepthCm": "<itemDepthCm>",
      "itemHeightCm": "<itemHeightCm>",
      "innerWidthCm": "<innerWidthCm>",
      "innerDepthCm": "<innerDepthCm>",
      "innerHeightCm": "<innerHeightCm>",
      "paddingCm": "<paddingCm>"
    },
    "name": "tds_purchase_m_yamazaki_wood_top_slipper_rack"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/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. Beyond that, the description adds nothing about behavior: it does not say what the tool returns (a pass/fail verdict, a margin, a recommendation), how padding is applied, or what happens when the item exceeds the inner dimensions. The only extra content is a sourcing tip.

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 and free of padding, so there is no bloat to trim. However, it is under-specified rather than efficient: the lead sentence spends its space restating the product name instead of front-loading what the tool computes.

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?

With 8 required parameters, no output schema, and zero schema description coverage, the description needs to explain both inputs and the expected result. It does neither adequately: units, the item/inner geometry comparison, and the return value are all unstated, so an agent cannot predict the outcome of a call.

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% across 8 required numeric/string parameters, so the description carries the full explanatory burden. It clarifies only offeredModel ('seller's model field or exact variant name') and gestures at paddingCm via 'required clearances'. It never explains the item* versus inner* distinction, the unit (cm), or how width/depth/height pairs are compared, leaving six parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Recorded model Wood-Top Slipper Rack', which mostly restates the title's product name, and never states the operation. There is no verb such as 'check' or 'verify' and no mention of a fit verdict, so an agent must infer the purpose from the tool name alone. It is distinguishable from siblings only by the product name, not by function.

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 sentences 'Use the seller's model field or exact variant name' and 'Use measurements for the exact variant' are input-sourcing hints, not when-to-use guidance. Nothing says when this fit-check applies versus alternatives such as tds_accessory_fit_through_lip, tds_quote_storage_space, or the many tds_purchase_m_* product tools. No prerequisites or exclusions are given.

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.