Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman 16 oz. Pulse Pump

tds_purchase_m_simplehuman_pulse_pump_16_oz
Read-onlyIdempotent

Recorded model 16 oz. Pulse Pump. 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_pulse_pump_16_oz"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds nothing beyond that: it never says what the tool returns (a fit verdict?), how padding is applied, or what happens when an item exceeds the inner space. The 'required clearances' phrase hints at a buffer but does not explain it.

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 with no filler, and the product identity is front-loaded. However, the opening sentence ('Recorded model 16 oz. Pulse Pump') mostly restates the title and name, so the limited space is spent on redundancy rather than on the mechanics of the fit check.

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?

An 8-required-parameter tool with zero schema descriptions, no output schema, and annotations covering only safety needs a description that explains the fit computation and clearance semantics. It omits both, leaving an agent to guess how item, inner, and padding values combine and what the result means.

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 all 8 required parameters, so the description must carry the load and largely does not. It only clarifies offeredModel (seller's model field or exact variant name) and loosely gestures at paddingCm via 'required clearances'; it never distinguishes itemWidthCm/itemDepthCm/itemHeightCm from innerWidthCm/innerDepthCm or states that padding applies per side.

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 title says 'Check storage fit' and the description pins the product ('16 oz. Pulse Pump'), but the description body never states the operation — that it compares item dimensions against inner dimensions with a clearance buffer. The only verbs are instructions about which inputs to supply, so the actual purpose is inferred from the title rather than stated.

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?

It tells the agent to use the seller's model field or exact variant name and to use measurements for that variant, which is input-selection guidance, not usage guidance. There is no statement of when to call this versus the many sibling product-fit tools or tds_accessory_fit_through_lip, no prerequisites, and no exclusions.

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.