Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Deflecto Clear Two-Drawer Stackable Cube Organizer

tds_purchase_a14
Read-onlyIdempotent

Recorded model 350101. 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>",
      "desktopWidthCm": "<desktopWidthCm>",
      "productWidthCm": "<productWidthCm>",
      "leftMarginCm": "<leftMarginCm>",
      "rightMarginCm": "<rightMarginCm>"
    },
    "name": "tds_purchase_a14"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/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 the safety profile is covered. Beyond that the description only insists on exact-variant matching and 'required clearances', giving no sense of what is computed, recorded, or returned for the five supplied measurements.

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, so it is tight. However, the guidance is front-loaded with a bare model number rather than a statement of function, leaving the reader without a frame for the following sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Annotations fully cover the read-only/idempotent character and there is no output schema to explain, which lowers the burden. Still, for a five-parameter, zero-coverage, closed-world computation tool, the definition omits the essential context of what result the clearance measurement produces, leaving the definition adequate but thin.

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% with five required numeric/string parameters, so the description must carry the load. It hints that offeredModel should match the seller's model and that measurements must be for the exact variant including clearances, but it never explains what desktopWidthCm, productWidthCm, leftMarginCm or rightMarginCm individually mean or how they interact (e.g., whether margins are added to product width against desktop width).

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 actually does — it only says 'Recorded model 350101' and gives input advice. The name 'tds_purchase_a14' is opaque, and while the title mentions 'Plan working clearance', an agent reading the description alone cannot tell whether this purchases, records, or computes a fit for the organizer.

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 sentences 'Use the seller's model field or exact variant name' and 'Use measurements for the exact variant' are input-format instructions rather than when-to-use guidance. There is no indication of when this tool applies versus the many sibling drawer/organizer tools, nor any prerequisite or exclusion.

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.