Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Pitch Side Chair

tds_purchase_m_poppin_pitch_side_chair_109680
Read-onlyIdempotent

Recorded model Pitch Side 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_side_chair_109680"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds nothing beyond that: it does not say whether a clearance plan is stored, recomputed, or merely returned, nor how the clearance values relate to the supplied measurements, which matters given the name says "recorded".

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 and the product identity front-loaded, but the brevity comes at the cost of substance rather than being tight and informative. Nothing is wasted, yet nothing is well-structured either.

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?

No output schema exists and five required numeric parameters are undocumented, so the description should explain the clearance calculation inputs and return behavior; it does neither. For a calculation-style tool this leaves the agent guessing how to set margins and widths correctly.

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 all five required parameters, so the description must compensate and largely does not. It hints that offeredModel should be the seller's model/variant string and that measurements must match that variant, but leftMarginCm, rightMarginCm, desktopWidthCm, and productWidthCm are never distinguished or given units/relationships.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (Pitch Side Chair) via "Recorded model Pitch Side Chair" but never states a verb or the actual action — working-clearance planning — which only appears in the title. An agent can see which product this tool is about but not confidently what the call produces.

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-selection hints, not usage guidance. There is no statement of when to choose this tool over the sibling chair tools (sled chair, scoop chair, nomad task chair) or any preconditions/exclusions.

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.