Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman Sensor Pump Foam

tds_purchase_m_simplehuman_sensor_pump_foam
Read-onlyIdempotent

Recorded model Sensor Pump Foam. 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_sensor_pump_foam"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), so the bar is lower. The description adds one behavioral hint — that the check incorporates "required clearances" (i.e., padding affects the result) and that measurements must match the exact variant — but says nothing about how the fit verdict is produced or what a passing/failing outcome means.

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?

Only three short sentences, so nothing is bloated, but the leading sentence is a label that carries no actionable information and pushes the useful input guidance behind it. Front-loading the actual check-and-fit statement would cost nothing.

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 a computation tool with 8 required numeric/string parameters, 0% schema coverage, and no output schema — meaning the description should explain both the item-vs-interior dimension split and what result comes back. It does neither, so an agent must guess at semantics that determine correctness.

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 must carry the load. It clarifies only offeredModel (seller's model field or exact variant name) and hints at paddingCm via "required clearances"; it never explains the critical item*Cm vs inner*Cm distinction (item dimensions vs container interior) or the centimetre units, leaving the most error-prone parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recorded model Sensor Pump Foam" restates the tool name/title rather than stating what the tool does; the actual operation (checking whether an item's dimensions fit inside a storage space, with clearances) must be inferred from the title and the parameter names. No verb+resource statement appears in the description itself.

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 guidance ("use the seller's model field or exact variant name", "use measurements for the exact variant") is about how to fill inputs, not when to choose this tool over the many sibling purchase/fit tools. No exclusions, prerequisites, or routing cues are given.

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.