Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Desk Mat Pro Slim

tds_purchase_m_orbitkey_desk_mat_slim
Read-onlyIdempotent

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

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 fully covered elsewhere. The description adds nothing beyond that — it does not say what is computed or recorded, whether the result is stored, or what validation happens when the model name mismatches a variant.

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 padding, and the model-identification rule comes first. However the brevity is bought by under-specification rather than efficient phrasing — the sentences are terse hints, not a front-loaded statement of purpose.

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 parameters at 0% schema coverage and no output schema, the description should explain the fit/clearance calculation and the meaning of each dimension. It instead provides two generic hints, so an agent cannot confidently construct a valid call or interpret the result.

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% and all five parameters are required, so the description carries the full burden. It loosely maps "seller's model field or exact variant name" to offeredModel and "measurements ... including required clearances" to the four numeric fields, but never explains which number is the desk width versus the mat width versus the margins, leaving the agent to infer from property names alone.

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 Slim" restates the product name in the title rather than stating an action. The description never says what the tool does with the model and measurements — record a purchase, validate a fit, compute clearance — so the agent must guess the verb from the title 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?

"Use the seller's model field or exact variant name" and "use measurements for the exact variant" are input constraints, not when-to-use guidance. No condition distinguishes this tool from the many sibling purchase-model tools, and no prerequisites or exclusions are given.

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.