Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Command Clear Round Cord Clips

tds_purchase_a19
Read-onlyIdempotent

Recorded model 17017 Clear Round Cord Clips. 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_a19"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the agent knows this is a safe, repeatable lookup/plan step without side effects. The description adds nothing beyond that — no indication of what is computed, what happens on an unmatched model, or whether the clearance figures are validated — but with full annotation coverage the bar is lower.

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?

Two short sentences with no filler and the product identity front-loaded. The brevity works against it, however: the space saved is spent nowhere, leaving the core action unstated rather than being tight and informative.

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

Completeness1/5

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

Five required numeric parameters with zero schema descriptions, no output schema, and a non-obvious clearance computation make this a case where the description must do heavy lifting. It supplies only a product name and vague input hints, leaving an agent unable to call the tool correctly from the text alone.

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%, so the description must carry all five parameters, and it only gestures at them: offeredModel is loosely covered by "seller's model field or exact variant name," and the four numeric fields by "measurements for the exact variant, including required clearances." It never distinguishes desktopWidthCm from productWidthCm or explains what left/right margin mean in the clearance calculation.

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 identifies a product ("Recorded model 17017 Clear Round Cord Clips") and an input convention, but never states a verb or what the tool actually does — no mention of planning clearance, checking fit, or producing measurements. The only signal about the operation lives in the title, not the description, so an agent cannot tell from the text what calling this returns.

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" is input-format guidance, not when-to-use guidance. There is no statement of when this tool applies versus the many sibling tds_purchase_* tools, and no exclusions or alternatives are named.

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.