Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Key Scoop Chair

tds_purchase_m_poppin_key_scoop_chair_108964
Read-onlyIdempotent

Recorded model Key Scoop 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_key_scoop_chair_108964"
  }
}

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing behavioral — it never explains what "planning clearance" produces, how the margins are used, or what the result represents. It does not contradict the annotations, but it also contributes no context beyond them.

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 little wasted phrasing, but the first sentence is pure filler that duplicates the product name already in the title. The input guidance is front-loaded but too terse to be actionable.

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?

For a five-parameter calculation tool with no output schema and no schema descriptions, the definition is underspecified: it does not explain what is computed from the measurements or what the caller receives. The agent has enough to fill fields but not enough to predict the result.

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 carries the full burden, and it only loosely maps inputs: "model field or exact variant name" points to offeredModel, and "measurements... including required clearances" gestures at the four cm fields. It never distinguishes desktopWidthCm from productWidthCm, nor explains that left/right margins are clearances, leaving the agent to guess the mapping.

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 restates the product name ("Recorded model Key Scoop Chair") without stating what the tool actually does. The title says "Plan working clearance," but the description contains no verb describing the operation — it only gives input instructions. An agent cannot tell from the text whether this records, computes, or looks up clearance data.

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" and "Use measurements for the exact variant" are input-selection hints, not when-to-use guidance. There is no statement of when this tool applies versus alternatives, nor any prerequisite or exclusion. The agent must infer applicability entirely from the product name.

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.