Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Sterilite 14 Gallon Footlocker

tds_purchase_a03
Read-onlyIdempotent

Recorded model 2212. 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_a03"
  }
}

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 safety is covered. Beyond that the description discloses nothing behavioral: no pass/fail criteria, no indication of what happens when the item does not fit, no mention of tolerance or clearances handling in the result.

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 2212' spends the prime front-loaded position on an unexplained token instead of stating what the tool does.

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?

An 8-parameter, fully required, closed-world evaluation tool with no output schema needs the description to explain the fit computation and result shape. The description instead gives fragmentary input advice, leaving the core semantics — how item dimensions, inner dimensions and padding combine — entirely unstated.

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 coverage is 0% across 8 required parameters, so the description carries the full burden. It clarifies offeredModel (seller's model field or exact variant name) and hints at paddingCm ('required clearances'), but leaves the six item/inner width, depth and height dimensions — the crux of a fit check — undefined as to which is the container versus the contents.

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 title identifies the product (Sterilite 14 Gallon Footlocker) and 'Check storage fit', but the description itself never states a verb+resource or says what the tool returns. 'Recorded model 2212' is opaque — it is unclear whether this validates fit, records a purchase, or logs a measurement against a known model.

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' gives input sourcing advice, not when-to-use guidance. With twenty near-identical siblings (tds_purchase_a04 through a22) plus tds_accessory_fit_through_lip and tds_quote_storage_space, no condition selects this tool over another.

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.