Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · IRIS USA 4 × 6 Photo Storage Box with 16 Inner Cases

tds_purchase_a06
Read-onlyIdempotent

Recorded model 587062 — Transparent Craft Keeper. 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_a06"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description need not restate safety. It adds that fit must be based on the exact variant and include required clearances, a useful behavioral constraint, but says nothing about how fit is evaluated or what result is produced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short, but the first sentence is a cryptic product note ('Recorded model 587062 — Transparent Craft Keeper') that is not front-loaded with the tool’s purpose. The remaining fragments are concise but read as schema guidance rather than a coherent definition.

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?

With eight required parameters, no output schema, and zero schema descriptions, the definition should explain the fit-check logic, how item and inner dimensions are compared, and how padding is applied. It leaves these core semantics to inference, so it is not complete enough for reliable invocation.

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 eight required parameters. The description only clarifies offeredModel as the seller’s model field or exact variant name and generically says to use exact-variant measurements including clearances; it does not explain item versus inner dimensions or the role of paddingCm.

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 never states that the tool checks storage fit; it opens with 'Recorded model 587062 — Transparent Craft Keeper' and then gives input instructions. Only the title supplies the actual purpose, so an agent reading the description alone cannot reliably identify the verb and resource.

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?

It tells the caller to use the seller’s model field or exact variant name and exact-variant measurements including clearances, but gives no when-to-use, when-not-to-use, or sibling-alternative guidance. Those are input instructions, not tool-selection guidance.

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.