Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman Sensor Pump Duo

tds_purchase_m_simplehuman_dual_rechargeable_liquid_117a2ae4
Read-onlyIdempotent

Recorded model Sensor Pump Duo. 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_dual_rechargeable_liquid_117a2ae4"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description adds only a caution about using exact-variant measurements; it does not say what the tool returns (fit/no-fit, margins, failures) even though there is no output schema to fall back on.

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 model identity is front-loaded. However, the terseness comes at the cost of under-specification — the sentences are terse without being informative.

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 an 8-required-parameter, 0%-coverage, no-output-schema tool, the definition is not complete enough: the computation, the meaning of the clearance value, and the return shape are all left unexplained. An agent could construct the call from parameter names alone but could not predict or interpret the result.

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 only addresses offeredModel (use seller's model field or exact variant name) and gestures at clearances for paddingCm; it never explains the item-vs-inner measurement pairs, units, or how padding is applied. Two of eight parameters get any real meaning added.

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?

The description names the recorded product ("Sensor Pump Duo") but never states the operation the tool performs — nothing says it computes whether the item fits inside the given inner dimensions. The actual purpose (storage-fit check) is only inferable from the title and the item/inner/padding parameter names, not from 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?

"Use the seller's model field or exact variant name" is data-entry guidance, not when-to-use guidance. With dozens of sibling product tools, nothing explains when a fit check is appropriate versus a plain product lookup, or what to do if the variant is unknown.

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.