Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman Double X-Frame Hamper

tds_purchase_m_simplehuman_double_x_frame_hamper
Read-onlyIdempotent

Recorded model Double X-Frame Hamper. 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_simplehuman_double_x_frame_hamper"
  }
}

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds a genuine behavioral constraint — values must correspond to the exact variant and must include clearances — but says nothing about what the computation returns (fit verdict, margin, failing dimension) or how mismatch is reported.

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?

Two short sentences with no padding, which is appropriate. But the opening "Recorded model Double X-Frame Hamper" essentially restates the name/title and occupies the front-loaded position that should carry the operation, so the most important information is not where it belongs.

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 eight-required-parameter geometric fit calculation with no schema descriptions, no output schema, and no explanation of the item-vs-inner dimension model or the fit rule. For a computation tool whose entire value is the derived result, the definition leaves both the input semantics and the expected outcome underspecified.

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%, so the description carries the full burden for 8 cryptic, all-required parameters. It only sheds light on two: offeredModel (the seller's model field or exact variant name) and paddingCm (implied by "required clearances"). The critical distinction between itemWidthCm/itemDepthCm/itemHeightCm and innerWidthCm/innerDepthCm/innerHeightCm is left entirely unexplained.

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 product ("Double X-Frame Hamper") but never states the operation performed — the verb only appears in the title ("Check storage fit"), not in the description text. An agent knows which product this covers but must infer from parameter names that the tool evaluates whether the hamper fits inside given inner dimensions plus padding.

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?

"Use the seller's model field or exact variant name" and "Use measurements for the exact variant, including required clearances" give real input-selection guidance for a variant-specific product. However, there is no guidance on when this tool should be chosen versus the sibling single X-frame hamper check, nor any exclusions or preconditions.

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.