Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Clip Mini

tds_purchase_m_orbitkey_clip_mini
Read-onlyIdempotent

Recorded model Clip Mini. 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_clip_mini"
  }
}

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 establish a safe read-only, idempotent operation, so the description need not restate safety. However, it does not explain what is calculated, what a successful result means, or how required clearances affect the outcome.

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?

The description is short and avoids filler, but it is not front-loaded with a clear statement of what the tool does. The opening phrase "Recorded model Clip Mini" is ambiguous and does not orient the agent before the parameter advice.

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 five-parameter required-input tool with no output schema and no parameter descriptions in the schema, the description is incomplete. It does not explain the clearance computation, measurement assumptions, or what result the caller should expect.

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 must compensate, but it only clarifies the model field and vaguely references measurements and required clearances. It does not explain the roles of desktopWidthCm, productWidthCm, leftMarginCm, rightMarginCm, or their units.

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 says "Recorded model Clip Mini" but never states the core action: recording, computing, validating, or planning a clearance. It identifies the product variant, but the verb and resulting behavior remain unclear.

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?

It gives parameter-selection advice for the model and variant, but no when-to-use guidance, prerequisites, or comparison to alternatives. The agent is not told when this clearance-planning tool is appropriate versus related purchase or planning tools.

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.