Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Desk Mat Pro

tds_purchase_a20
Read-onlyIdempotent

Recorded model Desk Mat Pro. 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_a20"
  }
}

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the tool validates fit or just records inputs, what happens when margins are insufficient, or how it relates to the 'purchase' naming even though it is a read-only planning call.

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 at two sentences with no filler, which is good. But the brevity comes from under-specification rather than tight editing: the opening fragment is not front-loaded with a verb, and the second sentence packs several distinct instructions without structure.

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, unit-bearing parameters, zero schema descriptions and no output schema, the description should carry nearly all the explanatory burden but does not. An agent cannot tell what a valid call looks like (e.g. whether productWidthCm must be <= desktopWidthCm minus margins) or what the call returns.

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 numeric/string parameters with no units, ordering or relationships documented. The description only hints that offeredModel comes from a seller's model field and that the cm-valued parameters are "measurements ... including required clearances", leaving desktopWidthCm, productWidthCm, leftMarginCm and rightMarginCm individually undefined.

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 Desk Mat Pro" is a noun fragment that largely restates the title and product name rather than stating what the tool does with the inputs. It never says that it records or plans a clearance fit from desktop width, product width and margins, so the agent must infer the operation from parameter names 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?

The description gives input-sourcing advice ("use the seller's model field or exact variant name") but no when-to-use, when-not-to-use, or alternative guidance. It does not distinguish this desk-mat clearance tool from the many sibling purchase tools, including the other Orbitkey desk mat variants.

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.