Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Slim Storage Box — Steel + Wood

tds_purchase_a17
Read-onlyIdempotent

Recorded model Slim Storage Box Steel + Wood. 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_a17"
  }
}

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, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing beyond that: no explanation of what the tool evaluates, how clearances are applied, what tolerance is used, or what a result means. The words "Recorded" and the tds_purchase_ prefix sit in mild tension with readOnlyHint, though "recorded" reads as a data label rather than a write claim.

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?

It is short and front-loads the variant-identification rule, so there is no padding. But the terseness crosses into under-specification: three clipped sentences that read like notes rather than a definition.

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 mandatory parameters at 0% schema coverage and no output schema, the description needs to explain both the fit computation and each dimension's meaning. It does neither, leaving the agent to guess how outer vs inner dimensions and padding combine into a verdict.

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 parameters, so the description must carry the burden. "Measurements for the exact variant, including required clearances" gives a partial hint that paddingCm represents clearance, but it never distinguishes itemWidthCm/itemDepthCm/itemHeightCm from innerWidthCm/innerDepthCm/innerHeightCm — the most consequential ambiguity for a fit check.

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 names the product ("Slim Storage Box Steel + Wood") but never states the action. "Recorded model" is a fragment, not a verb, so an agent cannot tell whether this tool records a purchase, evaluates whether the box fits a space, or returns a fit verdict — despite the title hinting at "Check storage fit."

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 give input-sourcing advice (use the seller's model field or exact variant name, use measurements for the exact variant) rather than when to call this tool versus a sibling. No conditions, exclusions, or alternative routing are offered for the many tds_purchase_* siblings.

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.