Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · simplehuman studio in-cabinet can

tds_purchase_m_simplehuman_studio_in_cabinet_can
Read-onlyIdempotent

Recorded model studio in-cabinet can. 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_studio_in_cabinet_can"
  }
}

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
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 safety is covered. The description adds no behavior beyond that — nothing about what the result expresses (fit/no-fit), how clearance/padding is applied, or tolerance behavior. With no output schema present, silence on the return value is a meaningful gap.

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, but the opening "Recorded model studio in-cabinet can." is a fragment that restates the title rather than front-loading the operation. The most decision-relevant content (what the fit check does) is absent while input advice occupies both remaining sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only computation this is close to adequate, but with 8 required undocumented parameters and no output schema, the description should explain which dimensions pair with which and what the tool returns. As written, an agent must guess at the geometric model behind the comparison.

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 numeric/string parameters, so the description must compensate and only partly does. It signals that offeredModel takes a seller model/variant name and that dimensions must include "required clearances" (paddingCm), but it never distinguishes itemWidth/Depth/Height from innerWidth/Depth/Height, nor clarifies that padding is a per-side clearance nor the unit convention beyond the parameter suffix.

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 model ("studio in-cabinet can") but never states the actual operation — the title says "Check storage fit," while the description body only talks about model naming and measurements. An agent can infer a fit/compatibility check from the parameter set (item vs. inner dimensions plus padding), but the verb is not stated explicitly. It is distinguishable from siblings only because they are other products' fit checks/records.

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 input-sourcing guidance and imply the tool applies to one specific variant at a time. However, there is no statement of when to call this versus a sibling fit tool, and no exclusions or prerequisites (e.g., only for in-cabinet placement).

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.