Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Single Letter Tray

tds_purchase_a18
Read-onlyIdempotent

Recorded model Single Letter Tray. 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_a18"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's remaining burden is to explain what the call actually produces or enforces. It offers nothing about the clearance computation, units, tolerance behavior, or result shape, only a vague note about "required clearances."

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, so it is not bloated. However the brevity is under-specification rather than efficiency: the opening sentence is a product restatement that carries no actionable information for invoking the tool.

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?

With five fully-undocumented required parameters, no output schema, and a geometrically constrained computation (margins plus product width against desktop width), the definition omits nearly everything an agent needs. The single constraint that matters — that the clearances must fit — is only alluded to as "including required clearances."

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 their meaning. It hints that offeredModel expects the seller's model or exact variant name, but says nothing about desktopWidthCm, productWidthCm, leftMarginCm, or rightMarginCm — not even that margins/sum must fit the 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 a verb or what is computed; "Recorded model Single Letter Tray" restates the product in the title rather than the operation. An agent cannot tell from this text whether the tool plans clearance, records a purchase, or validates dimensions — only the title hints at "Plan working clearance."

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 input-format advice ("Use the seller's model field or exact variant name"), with no statement of when this tool applies versus alternatives such as the double-tray or other purchase siblings. No prerequisites, exclusions, or conditions for choosing it are given.

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.