Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Desk Mat

tds_purchase_m_orbitkey_deskmat
Read-onlyIdempotent

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

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 safety is covered. The description adds only the constraint that measurements must include required clearances for the exact variant, with no statement of what is computed, validated, or returned.

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, but the opening line 'Recorded model Desk Mat' carries no actionable information and is placed where the core purpose should be. The parameter hints follow in reasonable order.

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?

A read-only computation with five mandatory measurements and no output schema needs the description to explain the computation and result; instead an agent learns nothing about what a successful call produces. The tool is underspecified relative to its complexity.

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, so the description must carry the load. It clarifies offeredModel (seller's model field or exact variant name) and alludes to the measurement fields via 'including required clearances', but never explains desktopWidthCm vs productWidthCm or how left/rightMarginCm should be derived.

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 never states a verb or the outcome of the call; 'Recorded model Desk Mat' merely restates the product in the title. Only the title 'Plan working clearance' hints at the operation, and the tool name (tds_purchase_m_...) suggests purchasing, leaving the actual purpose ambiguous.

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?

No when-to-use guidance or exclusions are given; the sentences 'Use the seller's model field or exact variant name' and 'Use measurements for the exact variant' are data-entry rules, not usage policy. Nothing distinguishes this from the sibling desk-mat variant tool (tds_purchase_m_orbitkey_desk_mat_slim) or from tds_quote_framing_plan.

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.