Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Tall Umbrella Stand

tds_purchase_m_yamazaki_tall_umbrella_stand
Read-onlyIdempotent

Recorded model Tall Umbrella Stand. 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_tall_umbrella_stand"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 without help. The description adds only the hint that clearance/padding matters to the evaluation; it never states what the tool actually returns (a fit verdict? a boolean? a delta?) or how the comparison is performed, which is the key behavioral unknown for a check-style tool with no output schema.

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?

Three short sentences, so there is no bloat, and the constraint about using the exact variant is reasonably front-loaded. However, the opening sentence ("Recorded model Tall Umbrella Stand") earns no place since it duplicates the title, displacing space that could have explained the parameters or the returned verdict.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a product-specific fit check with four annotation hints already covering safety and eight required numeric parameters, the description is broadly adequate: it names the identifier source and insists on exact-variant measurements with clearances. Its remaining gaps — the interior vs exterior field distinction and the nature of the result — are real but modest, since the parameter names themselves signal measurements in centimeters.

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 eight required parameters, so the description carries the full burden. It maps offeredModel to "seller's model field or exact variant name" and groups the numeric fields as "measurements... including required clearances," but it never explains the critical distinction between itemWidthCm/itemDepthCm/itemHeightCm (the object) and innerWidthCm/innerDepthCm/innerHeightCm (the storage cavity), nor what paddingCm does or what units are expected. Half the semantics needed to call this correctly are absent.

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 never uses a verb; "Recorded model Tall Umbrella Stand" largely restates the title and product name. The following sentences hint that the tool takes a model identifier plus measurements to evaluate fit against a storage space, but the agent must infer that from parameter language rather than a stated purpose. It is distinguishable from generic Yamazaki purchase/shelf siblings only via the product name, not via an explicit goal statement.

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 guidance on which identifier to supply ("seller's model field or exact variant name") and insists measurements be for that exact variant, including clearances. What is missing is when to use this fit-check versus other approaches, any prerequisites (e.g. that the stand must already be identified), or any exclusions. Usage is implied rather than framed as when/when-not.

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.