Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Yamazaki Beautes Headphone Stand

tds_purchase_a25
Read-onlyIdempotent

Recorded model Beautes Round Headphone 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_a25"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what the tool produces (a placement plan, a pass/fail fit check, warnings), what happens when the stand plus margins exceed the desktop width, or whether invalid variants are rejected. For a computation tool with no output schema, this is a meaningful gap.

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?

Three short sentences with no filler and the model-identification rule front-loaded. The brevity is appropriate, though some of the space is spent on input rules rather than on stating what the tool does.

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?

With five required numeric parameters, 0% schema coverage, and no output schema, the description should explain units, the fit constraint, and the result shape. It covers only model identification and a vague reference to clearances, leaving an agent unable to predict validation behavior or output.

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 only partially meets it. It clarifies offeredModel (seller's model field or exact variant name) and hints that the margin parameters are 'required clearances', but never distinguishes desktopWidthCm from productWidthCm, and never states the core fitting relationship (product width plus both margins versus desktop width) that determines whether inputs are valid.

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 description names a specific product ('Recorded model Beautes Round Headphone Stand') but never states the action with a verb — it does not say it computes a clearance plan, checks fit, or returns a recommendation. An agent must infer the purpose from the parameter set (desktopWidthCm, productWidthCm, leftMarginCm, rightMarginCm). The resource is identifiable; the operation is not.

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 real input-selection guidance for offeredModel, and 'Use measurements for the exact variant' scopes the numeric inputs. However, there is no guidance on when to pick this tool rather than a sibling per-product clearance tool, and no prerequisites or exclusions are stated.

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.