Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman Single X-Frame Hamper

tds_purchase_m_simplehuman_single_x_frame_hamper
Read-onlyIdempotent

Recorded model Single 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_single_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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds that this is a recorded model keyed to a specific variant and that clearances must be included, but it says nothing about what a fit result looks like or what happens when the supplied measurements do not fit.

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?

Three short sentences with no filler, and the model identification is front-loaded before the input-sourcing rules. The opening sentence largely restates the title, which is the only wasted space.

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 numeric parameters, no output schema, and no annotation coverage of geometry, the description should explain the measurement model (what item vs inner dimensions mean, how padding applies). It omits this entirely, leaving an agent unable to confidently populate half the required inputs.

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 parameters, so the description carries the full burden. It clarifies only two things — offeredModel maps to the seller's model field/exact variant name, and paddingCm represents required clearances — and leaves the critical item*Cm versus inner*Cm distinction (external footprint vs internal capacity) 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 identifies the recorded product ("Single X-Frame Hamper") and implies a storage-fit evaluation, but it never states the action with a verb — the intent (checking whether this hamper fits in a space) must be inferred from the title rather than the description. It also does not distinguish this tool from the many other per-product fit tools in the sibling list, beyond the model name itself.

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" give real guidance on how to source inputs correctly, which is more than nothing. However, there is no when-to-use/when-not guidance and no explicit statement of when an agent should prefer this per-model tool over a generic fit or search tool.

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.