Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman Square Push Pump

tds_purchase_m_simplehuman_square_push_pump
Read-onlyIdempotent

Recorded model Square Push 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_square_push_pump"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds that the seller model field or exact variant name must be used and that required clearances must be included, but it does not explain how measurements are evaluated or what the tool returns.

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?

The description is two short sentences with no obvious filler. However, it is not strongly front-loaded because the first sentence identifies a model without stating the tool's action or output, so the agent must read further and still infer the purpose.

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?

For a tool with eight required numeric parameters, no output schema, and 0% schema description coverage, the description is too thin. It lacks an explanation of the fit calculation, the roles of item versus inner dimensions, and the meaning or effect of padding/clearances.

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% for eight required parameters. The description partially clarifies offeredModel and the general need for measurements including clearances, but it does not distinguish itemWidthCm/itemDepthCm/itemHeightCm from innerWidthCm/innerDepthCm/innerHeightCm or explain paddingCm, leaving key semantics undocumented.

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 and first sentence identify the exact product (Square Push Pump), and the instruction to use the seller model or exact variant implies a fit-check workflow. However, the description itself never states the action clearly—checking whether the item fits storage—or what result is produced, so its purpose is only inferable with title help.

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 description tells the agent which model name and measurements to supply, but it does not explain when to use this tool versus alternatives or what conditions make it the right choice. With many sibling product tools, that selection guidance is missing.

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.