Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Honey-Can-Do Black 10-Drawer Rolling Storage Cart

tds_purchase_a11
Read-onlyIdempotent

Recorded model CRT-08654. 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_a11"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/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 the safety profile is fully covered structurally. The description adds nothing behavioural on top: it does not say what the tool returns (a fit/no-fit result?), how padding/clearance is applied, or what happens on failure, which is the exact gap annotations leave for a computation tool.

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 fluff, so it is efficiently sized. However the opening sentence ('Recorded model CRT-08654') is opaque and consumes the front-loaded position with information of unclear relevance rather than stating the operation.

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-required-parameter closed-world computation with no output schema needs the description to explain the result shape and the item-vs-container dimension semantics; it does neither. Relative to the tool's complexity, the definition is materially incomplete even though annotations cover the read-only profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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 carries the full burden and largely fails it. It alludes to offeredModel and to clearances (paddingCm) but never explains the crucial distinction between itemWidthCm/itemDepthCm/itemHeightCm and innerWidthCm/innerDepthCm/innerHeightCm, nor how paddingCm is applied or in what units.

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 a verb or the operation being performed; 'Recorded model CRT-08654' plus input-entry advice does not tell an agent whether this computes a fit verdict, stores a purchase, or validates measurements. Only the title ('Check storage fit') hints at the purpose, and the text does not differentiate it from siblings such as tds_landed_storage_cart or tds_quote_storage_space.

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 guidance given ('use the seller's model field or exact variant name', 'use measurements for the exact variant, including required clearances') is parameter-entry advice, not when-to-use guidance. There is no statement of when this tool applies versus fit-related siblings like tds_accessory_fit_through_lip or tds_quote_storage_space, and no exclusions.

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.