Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Bevel Trimmer Battery

tds_purchase_m_bevel_trimmer_battery
Read-onlyIdempotent

Recorded model Trimmer Battery. Use the seller’s model field or exact variant name. Enter prices in the same currency. Use the amount that will appear on the order.

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>",
      "pricePerPack": "<pricePerPack>",
      "unitsPerPack": "<unitsPerPack>",
      "alreadyIncluded": "<alreadyIncluded>",
      "totalUnitsNeeded": "<totalUnitsNeeded>"
    },
    "name": "tds_purchase_m_bevel_trimmer_battery"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

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 and determinism are covered. The description contributes real business rules beyond that: prices must be in a single consistent currency and must match the amount that will appear on the order. It does not, however, say what the call returns or whether anything persists, which matters for a tool named "purchase" that is annotated read-only.

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?

Four short sentences with no padding, which is appropriate in size. However, the front-loaded first sentence is the least informative one and the ordering puts input advice before any statement of purpose.

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 tool with five required, undocumented numeric parameters and no output schema depends entirely on the description, and it leaves three of five parameters undefined. An agent cannot tell how alreadyIncluded interacts with totalUnitsNeeded or how unitsPerPack affects the recorded plan, which is the crux of the call.

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 carries the full burden and only partially does so. It gives meaningful guidance for offeredModel (seller's model field or exact variant name) and pricePerPack (same currency, order amount), but unitsPerPack, alreadyIncluded and totalUnitsNeeded — the core quantity math — receive no explanation at all.

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 Trimmer Battery" restates the tool name and title rather than stating an action; there is no verb describing what the tool does (plan a purchase line, compute a quantity, etc.). The remaining sentences describe how to fill inputs, not the tool's purpose, so an agent cannot distinguish it from the ~30 sibling purchase-planning tools.

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?

No when-to-use guidance and no alternatives named. The closest sibling, tds_purchase_m_bevel_trimmer, is precisely the kind of tool a caller would confuse this with (battery vs. device), yet nothing explains the split. What is present ("use the seller's model field or exact variant name") is input-entry advice, not usage scoping.

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.