Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · iDesign Rain 9" Spinner Clear

tds_purchase_m_idesign_rain_two_spinner_clr
Read-onlyIdempotent

Recorded model Rain 9" Spinner Clear. 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_idesign_rain_two_spinner_clr"
  }
}

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only that the model is 'recorded', implying a cached/snapshot reference rather than a live lookup. It says nothing about what the fit computation does with the clearances or what a result looks like.

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 lead sentence spends space restating the model name from the title instead of front-loading what the tool does. The remaining content is thin relative to the space available.

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 an 8-required-parameter tool with no output schema and no explanation of the fit verdict, margins, or failure conditions. Given the complexity and the absence of return-value documentation, the description leaves an agent unable to know what to expect after calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 8 required parameters, so the description must carry the load, and it only partially does: it clarifies that measurements must be for the exact variant and that clearances are included, which hints at the role of paddingCm. The item vs. inner dimension pairs and unit conventions remain unexplained, leaving most parameter meaning to be guessed from names.

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' for a named product, and the description identifies the recorded model ('Rain 9" Spinner Clear') plus a hint about measurements and clearances. But the description never states an action verb or what the check produces, so the agent must infer a fit-evaluation from the title alone. It distinguishes this product variant from siblings but not the operation.

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 sentence 'Use the seller's model field or exact variant name' is input guidance, not when-to-use guidance. There is no statement of when this fit check applies versus alternatives like measurement-based clearance tools or other product variants, and no preconditions or exclusions 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.