Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Pitch Sled Chair

tds_purchase_m_poppin_pitch_sled_chair_104224
Read-onlyIdempotent

Recorded model Pitch Sled Chair. 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_m_poppin_pitch_sled_chair_104224"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/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 safety profile is covered. Beyond that the description adds only that measurements must be for the exact variant "including required clearances" — it does not say what is validated, what happens when the model name is unrecognized, or what the result conveys.

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 short and front-loaded, but the opening sentence squanders the lead on a restatement of the title instead of the actual operation, and the remaining two sentences are cryptic instructions rather than a coherent explanation. Brevity here reflects under-specification rather than disciplined editing.

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?

With five required parameters, zero schema descriptions and no output schema, the definition should explain the computation and expected result. Instead it leaves the agent guessing what the five numeric/string inputs combine into and what a valid call produces, which is inadequate for a tool whose whole value is a clearance calculation.

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 coverage is 0%, so the description must carry all parameter meaning, and it only gestures at two of the five: offeredModel (seller's model field or exact variant name) and required clearances (presumably leftMarginCm/rightMarginCm). It never explains desktopWidthCm vs productWidthCm, the units, or the 0–500 margin bounds.

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?

"Recorded model Pitch Sled Chair" restates the title rather than stating a verb and outcome; the closest thing to a purpose is the title's "Plan working clearance", but the description never says it computes or records a clearance fit between a desk and a chair. An agent cannot tell from the text whether this writes a record, calculates margins, or validates a product.

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?

It gives a narrow input hint ("use the seller's model field or exact variant name") and a measurement hint, but no when-to-use/when-not guidance and no differentiation from sibling product tools such as the other Poppin chair entries. The agent must infer the scenario entirely.

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.