Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Tech Organizer

tds_purchase_m_orbitkey_tech_organiser
Read-onlyIdempotent

Recorded model Tech Organizer. 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_tech_organiser"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds one real behavioral constraint: results depend on matching the exact recorded variant and on supplying measurements that include required clearances, which hints at correctness sensitivity. It says nothing about output, tolerances, or what happens with a mismatched variant or oversized margins.

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?

Two short sentences with no filler, but the first is a fragment ('Recorded model Tech Organizer.') that conveys product identity rather than the action, and the second lumps measurement guidance into one vague clause. Terse, front-loaded, yet under-informative rather than wasteful.

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 five-required-parameter planning/computation tool with no output schema and no annotation depth needs the description to explain inputs and expected result shape. Instead it leaves the four measurement parameters and the computed outcome unexplained, so an agent cannot confidently invoke it from the definition alone.

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 coverage is 0%, so the description must carry all param meaning, but it only clarifies offeredModel (seller's model field or exact variant name). The four numeric parameters — desktop width, product width, and the two margins — are never explained: units, whether left/right margins are the clearance gaps, or how they combine into a plan remain undocumented.

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 identifies the product ('Recorded model Tech Organizer') but never states the action the tool performs — planning/computing working clearance appears only in the title, not the description. It differentiates the product variant from siblings, but not the operation, so an agent cannot tell from the text what the call will actually produce.

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' is guidance about how to fill one parameter, not about when to use this tool rather than the Mini/Plus Tech Organizer variants or the quote/framing siblings. There are no stated preconditions, exclusions, or alternative-routing hints.

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.