Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Fellowes Booklift Copyholder

tds_purchase_a23
Read-onlyIdempotent

Recorded model 21100. 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_a23"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds only a narrow scope constraint — that the tool concerns the recorded model 21100 and the exact variant — without saying what is computed, what happens on mismatch, or what the caller receives.

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?

It is very short with no filler, but the size comes at the cost of clarity: the first sentence is an unexplained model number and the remaining two are terse imperatives. Nothing is wasted structurally, yet the content is too thin to be genuinely efficient.

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?

A five-parameter, all-required tool with no output schema and zero schema descriptions needs a description that explains the geometry inputs and the expected result. What is supplied is fragmentary and leaves the core computation opaque, so an agent cannot confidently construct a correct call from the definition 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% across five required parameters, so the description must carry the full explanatory burden and does not. It gestures at offeredModel ("seller's model field or exact variant name") and at the measurement parameters ("measurements for the exact variant, including required clearances"), but never explains units, how desktopWidthCm/productWidthCm relate to the left/right margins, or what a "required clearance" means in this context.

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 what the tool actually returns; it opens with the cryptic fragment "Recorded model 21100" and then gives input instructions. Only the title ("Plan working clearance · Fellowes Booklift Copyholder") conveys the purpose, and the description does nothing to distinguish this from the many sibling tds_purchase_aNN tools.

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?

There is no when-to-use guidance, no conditions or prerequisites, and no route to any alternative tool despite a large sibling catalog. The sentences present only input-preparation advice ("Use the seller's model field or exact variant name"), which is guidance about data entry rather than about tool selection.

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.