Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Double Tray

tds_purchase_m_poppin_double_tray_102977
Read-onlyIdempotent

Recorded model Double 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_m_poppin_double_tray_102977"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-destructive, idempotent, closed-world operation, lowering the disclosure burden. The description adds useful domain context that the exact variant and required clearances matter, but it does not explain what the tool returns or how the measurements are used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no obvious filler. The first sentence is oddly phrased, but the overall structure is efficient and the actionable guidance follows immediately.

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 tool with five required parameters, no schema descriptions, and no output schema, the description is too thin. It does not explain how the measurements and clearances are used, what the result represents, or what an agent should expect to receive.

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% for five required parameters, so the description must carry the full burden of explaining parameter meaning. It only generically references the seller's model field, exact variant name, measurements, and required clearances, without mapping these to offeredModel, desktopWidthCm, productWidthCm, leftMarginCm, or rightMarginCm.

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 title supplies the action ('Plan working clearance') and the product ('Poppin Double Tray'), but the description itself opens with the vague phrase 'Recorded model Double Tray' and never clearly states what the tool computes or returns. It does identify the resource and mentions exact variants and required clearances, so the purpose is inferable but not explicit.

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 description gives input guidance ('Use the seller’s model field or exact variant name' and 'Use measurements for the exact variant'), but it does not say when this tool should be used instead of alternatives. No sibling tools or exclusion conditions are mentioned, so an agent must infer usage from the product-specific 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.