Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Kikkerland Gator Phone Stand

tds_purchase_m_kikkerland_gator_phone_stand
Read-onlyIdempotent

Recorded model Gator 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_gator_phone_stand"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds only that the calculation involves "required clearances" for the exact variant; it does not say what is returned, whether the result is a fit verdict, or how desktop/margin values combine.

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 wasted clauses, but the lead sentence is redundant with the tool name and title, and the most decision-relevant content (exact-variant modeling, clearances) is pushed to the end rather than front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and five fully-required, undocumented parameters, the description should explain what the plan produces and how the numbers are interpreted. It covers the model-matching requirement and mentions clearances, but a caller still lacks enough to predict the result or understand the measurement 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% across five required parameters, so the description must carry the load. It clarifies offeredModel (seller's model field or exact variant name) and gestures at the clearance measurements, but never distinguishes desktopWidthCm from productWidthCm, nor explains that left/right margins are clearance from the desktop edge or what units are assumed.

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 carries the actual purpose ("Plan working clearance"), while the description opens with "Recorded model Gator Phone Stand," which largely restates the tool name rather than naming a verb and resource. The phrase "including required clearances" hints at what is computed, but an agent must infer the operation rather than read it plainly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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" gives concrete input-selection guidance, and "Use measurements for the exact variant" implies measurements must match the chosen variant. However, there is no statement of when to use this tool versus the many sibling purchase/plan tools, and no prerequisites or 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.