Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Kikkerland Pup Phone Stand

tds_purchase_m_kikkerland_pup_phone_stand
Read-onlyIdempotent

Recorded model Pup Phone Stand. 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_kikkerland_pup_phone_stand"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the description does not need to restate safety. It adds that the exact seller model/variant and exact measurements with required clearances matter, but it does not explain output, calculation behavior, validation, or failure conditions. This is minimally adequate because annotations carry the safety profile, but behavioral context beyond that is thin.

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?

The description is short and has no obvious padding, but the opening sentence is awkward and weakly front-loaded. The guidance is compact, though not structured around the action or the parameters in a way that makes the tool easy to invoke correctly.

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 required-input tool with no output schema and no parameter descriptions, the description is incomplete. It does not explain what the tool returns, how measurements are interpreted, or what constitutes a valid clearance plan, leaving key invocation details to the schema and the agent’s inference.

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 the burden for five required parameters. It gives some meaning for offeredModel (seller model field or exact variant name) and gestures at measurements/clearances, but it does not explain the relationships among desktopWidthCm, productWidthCm, leftMarginCm, and rightMarginCm or how the clearance calculation uses them.

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 largely restates the product name ("Recorded model Pup Phone Stand") rather than stating a clear action. The title says "Plan working clearance," but the description never explains whether the tool calculates clearance, records measurements, or returns a fit plan, so it is hard to distinguish behaviorally from sibling product tools.

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 input-population advice (use the seller’s model field or exact variant name, use exact-variant measurements including clearances) but no when-to-use guidance, exclusions, or comparison to alternatives such as other stand tools or quote/planning tools. The agent must infer the tool’s role from the product name alone.

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.