Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Goal Pinboard

tds_purchase_m_poppin_goal_pinboard_107341
Read-onlyIdempotent

Recorded model Goal Pinboard. 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_goal_pinboard_107341"
  }
}

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 cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description would only need to add what happens on call. It does not say whether this returns a pass/fail clearance verdict, a computed fit, or a stored record, despite there being no output schema to fall back on.

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, but the opening sentence is wasted space that conveys nothing actionable, and the useful guidance arrives only in the second and third fragments. No filler is excessive, yet the front-loading is poor.

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?

Five required numeric parameters, no schema descriptions, no output schema, and a non-obvious arithmetic relationship between desk width, product width, and margins are all left unexplained. For a computation-style tool this leaves an agent guessing at the input semantics.

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 must carry all five parameters. It only gestures at offeredModel and vaguely at "measurements... including required clearances", leaving desktopWidthCm vs productWidthCm vs leftMarginCm/rightMarginCm relationships and units undocumented.

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 Goal Pinboard" restates the title rather than stating what the tool does; there is no verb indicating a computation, lookup, or clearance calculation. Only the trailing clause about measurements hints that it relates fitting/clearance, and the agent cannot tell this apart from sibling purchase/plan tools from the text alone.

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?

No when-to-use or when-not-to-use guidance and no named alternative (e.g. the framing-plan sibling). The only directive is an input hint (use the seller's model field or exact variant name), which is guidance about arguments, not about tool selection.

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.