Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Utility Clip

tds_purchase_m_orbitkey_utility_clip
Read-onlyIdempotent

Recorded model Utility Clip. 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_utility_clip"
  }
}

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 declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds a meaningful constraint that measurements must be for the exact variant and include required clearances, but says nothing about validation, failure modes, or output behavior.

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, two sentences, and mostly free of fluff, but the opening fragment is awkward and not front-loaded with the action. The second sentence carries the only useful guidance.

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 planning tool with no output schema and no parameter descriptions, the definition should explain what is computed or returned and how clearances are evaluated. It leaves both the calculation semantics and the result shape unaddressed.

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 parameters. The description maps offeredModel loosely and groups the four measurement parameters as "measurements ... including required clearances," but it does not explain desktopWidthCm vs productWidthCm vs left/rightMarginCm or how they interact.

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 first sentence, "Recorded model Utility Clip," essentially restates the product name/title and supplies no verb or action. Only the second sentence hints at clearance planning by telling the caller to use measurements; an agent cannot tell from the description alone that this tool plans or validates working clearance.

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 input-selection advice ("seller's model field or exact variant name") but no when-to-use/when-not-to-use guidance and no alternative tools or conditions. Usage is only implied by the product-specific name.

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.