Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Orbitkey Toiletry Pouch

tds_purchase_m_orbitkey_toiletry_pouch
Read-onlyIdempotent

Recorded model Toiletry 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>",
      "desktopWidthCm": "<desktopWidthCm>",
      "productWidthCm": "<productWidthCm>",
      "leftMarginCm": "<leftMarginCm>",
      "rightMarginCm": "<rightMarginCm>"
    },
    "name": "tds_purchase_m_orbitkey_toiletry_pouch"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds a meaningful behavioral constraint — measurements must correspond to the exact variant, including required clearances — suggesting a validation step. It still does not disclose what the tool returns or what happens when clearances fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the model-identifier guidance is front-loaded. It is efficient, though the lead sentence wastes space restating the product name instead of stating the action.

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?

With five fully required, zero-documented numeric parameters, no output schema, and an ambiguous action, the description leaves too much for an agent to infer. A caller cannot confidently construct a valid measurement/clearance payload from this text 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 description coverage is 0% across five required parameters, so the description must carry the burden and largely does not. It vaguely maps to offeredModel and to the measurement fields, but never distinguishes desktopWidthCm from productWidthCm, never explains that left/right margins represent clearances, and gives no units or bounds guidance.

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?

"Recorded model Toiletry Pouch" restates the product name without a verb or stated outcome; nothing says whether the tool records a purchase, plans a layout, or validates clearances. The title hints at "Plan working clearance," but the description never confirms that action, so an agent cannot tell what calling it actually accomplishes.

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 sentences "Use the seller's model field or exact variant name" and "Use measurements for the exact variant" are input-format guidance rather than when-to-use guidance. There is no statement of when this tool applies versus the many sibling product tools, nor any prerequisite or exclusion.

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.