Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Boot Tray

tds_purchase_m_yamazaki_10490_apto_boot_tray
Read-onlyIdempotent

Recorded model Boot Tray. 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_10490_apto_boot_tray"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the description does not need to repeat the safety profile. It adds useful context that the exact variant and required clearances matter, but it does not explain what the fit check returns or how the measurements are evaluated, leaving an important behavioral gap.

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 no obvious filler. The opening fragment is somewhat vague, but the subsequent sentences are efficient and directly relevant to invocation.

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?

This is an 8-parameter, fully required measurement tool with no output schema, so the description should clarify the parameter roles and the expected fit-check result. It only says to use the exact variant and include clearances, which is not enough for an agent to invoke it confidently or understand what comes back.

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 all 8 required parameters, so the description must carry the burden of explaining them. It only generically references the seller's model field, exact variant measurements, and required clearances; it does not distinguish item dimensions from inner dimensions or define how paddingCm should be used.

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 names the exact product variant and implies a fit-checking use case through the title, but it never states the operation explicitly, such as calculating whether the item fits or validating measurements. The fragment 'Recorded model Boot Tray' identifies the resource but leaves the action vague.

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 gives invocation guidance about using the seller's model field or exact variant name and taking measurements for that exact variant, including clearances. It does not say when this tool should be used instead of alternatives, nor does it provide exclusions or selection criteria.

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.