Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Deflecto Stackable Caddy Organizer with Three Containers

tds_purchase_a13
Read-onlyIdempotent

Recorded model Stackable Caddy Organizer w/3 Containers. 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_a13"
  }
}

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
Behavior3/5

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

Annotations already disclose readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered without description help. The description adds nothing beyond that: it does not say what a call produces (a pass/fail fit result, a margin, a recommendation) or what happens when measurements exceed the caddy's dimensions, and there is no output schema to fall back on.

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 in length, but the first sentence is wasted on restating the product name already present in the title. The genuinely useful instruction about exact-variant measurements is buried after the redundant opener.

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?

For an 8-required-parameter fit-check tool with zero schema coverage and no output schema, the description is far too thin: it never defines the outer-vs-inner dimension contract or what a successful fit means. An agent could supply numbers but has no way to know whether they were interpreted correctly or what the result represents.

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% for all 8 required parameters, so the description carries the full burden and largely fails it. It clarifies offeredModel (seller's model field or exact variant name) and hints that measurements must be 'for the exact variant, including required clearances,' but never distinguishes itemWidthCm/itemDepthCm/itemHeightCm (outer) from innerWidthCm/innerDepthCm/innerHeightCm (inner), nor explains paddingCm semantics.

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 opens with 'Recorded model Stackable Caddy Organizer w/3 Containers,' which restates the product in the title rather than stating an operation. The title says 'Check storage fit' but the description never says the tool computes or returns a fit verdict, so an agent cannot tell from the description alone what action it performs versus siblings like tds_quote_storage_space 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?

The only guidance is about how to fill inputs ('Use the seller's model field or exact variant name'), not when to choose this tool over the fit/storage alternatives listed as siblings. There is no statement of preconditions, no exclusions, and no routing to a different tool for a different fit question.

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.