Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Orbitkey Desk Pouch

tds_purchase_a21
Read-onlyIdempotent

Recorded model Desk Pouch. 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>",
      "itemWidthCm": "<itemWidthCm>",
      "itemDepthCm": "<itemDepthCm>",
      "itemHeightCm": "<itemHeightCm>",
      "innerWidthCm": "<innerWidthCm>",
      "innerDepthCm": "<innerDepthCm>",
      "innerHeightCm": "<innerHeightCm>",
      "paddingCm": "<paddingCm>"
    },
    "name": "tds_purchase_a21"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds a useful behavioral constraint — that measurements must be for the exact variant including required clearances — but never states what the call returns (a fit verdict, a margin, a pass/fail) or how padding is applied.

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 little padding, but the opening fragment "Recorded model Desk Pouch." earns almost nothing and the substantive constraint about clearances is buried at the end rather than front-loaded.

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 an 8-required-parameter computation tool with no output schema and no schema descriptions, the definition should explain the measurement model (item envelope vs inner envelope, padding application) and the shape of the result. It does neither, leaving an agent unable to call it correctly without guessing.

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 8 required numeric parameters, so the description carries the full burden. It touches only offeredModel ("seller's model field or exact variant name") and gestures at paddingCm ("required clearances"), leaving the item-vs-inner dimension pairs (itemWidthCm/innerWidthCm, etc.) and whether padding is per-side or total completely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title supplies the actual purpose ("Check storage fit") for a specific product, but the description itself contains no verb at all — "Recorded model Desk Pouch" is a fragment that never states that this tool computes whether an item fits inside the pouch. An agent reading only the description body knows the product but must infer the operation.

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?

The only guidance is about input form: "use the seller's model field or exact variant name" and "use measurements for the exact variant." There is no statement of when to call this versus the many sibling purchase/fit tools (e.g. the limited-edition Desk Pouch variant), and no exclusions or preconditions.

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.