Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Sterilite 3 Drawer Wide Cart

tds_purchase_a05
Read-onlyIdempotent

Recorded model 3830. 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_a05"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. What the description adds is small but real: the notion of a 'recorded model' suggests the tool reconciles the offered model against a stored reference, hinting that a mismatch outcome is possible. It says nothing about what the result contains or whether a failing fit blocks a purchase.

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, which is good, but the lead sentence 'Recorded model 3830' is cryptic and lands before any statement of what the tool does. The remaining two sentences are near-duplicates in structure, each a bare imperative without explaining the underlying measurement model.

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 numeric/string parameters at 0% schema coverage, no output schema, and only safety annotations, the definition should explain the item/inner measurement distinction and how padding is applied. As written, an agent could supply values but could not confidently explain the outcome or fill the inner dimensions without guessing.

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%, so the description carries the full burden, yet it only speaks to offeredModel (seller's model field or exact variant name) and generically to measurements/clearances targeted at the exact variant. It does not explain the item-versus-inner (container) measurement pairing, what paddingCm represents, that units are centimeters, or what the required-clearance relationship means. Six of eight parameters remain semantically bare.

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 never names a verb or states that it computes a fit between the item and the drawer/cart; the only statement of intent comes from the title. 'Recorded model 3830' plus references to the seller's model and exact-variant measurements imply a fit/clearance check, but an agent must infer it. It also does not distinguish this from siblings such as tds_landed_storage_cart or tds_accessory_fit_through_lip.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives among the many similarly named purchase tools. The two sentences are instructions about how to populate arguments ('use the seller's model field', 'use measurements for the exact variant'), which is input hygiene rather than usage 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.