Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Sterilite Stack & Carry 2 Layer Handle Box & Tray

tds_purchase_a04
Read-onlyIdempotent

Recorded model 1412. 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_a04"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/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 safety is covered by structured data. The description adds nothing about what the call returns (fit verdict, margin, failure reason) or how padding affects the comparison. For a computation-style tool with no output schema, that output behavior is exactly what an agent needs and it is absent.

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 padding, so it is efficiently sized. However it is front-loaded with the cryptic "Recorded model 1412" rather than the operation, and the remaining sentences are directives rather than a coherent framing of the task.

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?

Eight required numeric/string parameters, no schema descriptions, no output schema, and no annotation help on results. Given that complexity, the definition should explain item-vs-container roles, padding semantics, and what a fit result looks like; it covers only the first partially and omits the rest.

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 parameters, so the description must compensate and largely does not. It maps loosely to offeredModel and paddingCm ("required clearances"), but never distinguishes the itemWidthCm/Depth/Height trio from the innerWidthCm/Depth/Height trio, which is the central ambiguity an agent must resolve to call this correctly.

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 what the tool does; it only instructs which model string and measurements to supply. The actual operation (checking whether an item fits inside a Sterilite Stack & Carry box given clearances) is only inferable from the title and the parameter names. The opaque name tds_purchase_a04 provides no help either.

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, including required clearances" give real guidance on how to populate inputs for this product family. There is no statement about when to prefer this tool over a sibling fit/purchase tool, but the variant-selection advice is concrete and actionable.

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.