Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Wahl Color Pro Rechargeable Clipper Kit

tds_purchase_d06
Read-onlyIdempotent

Recorded model 9649 / 09649P. 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_d06"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds almost nothing on top: it does not say what is computed or persisted, whether a plan is returned or merely validated, how quantities are derived, or what happens on idempotent re-calls. The currency hint is the only behavioural context provided.

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 — compact but poorly front-loaded: the lead is a model number rather than the tool's action. No sentence is wasted per se, but their ordering buries the guidance an agent needs first.

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 required parameters at 0% schema description coverage, no output schema, and a non-descriptive tool name, the description must carry the full explanatory burden and does not. The quantity parameters (unitsPerPack, alreadyIncluded, totalUnitsNeeded) are highly ambiguous — nothing explains that they combine to determine pack count — and the return value is undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No output schema, no annotations clarification needed; description covers offer model field selection ('seller's model field or exact variant name') and price currency semantics ('same currency', 'amount that will appear on the order'). It does not explain unitsPerPack, alreadyIncluded, or totalUnitsNeeded, but 4 is appropriate given the added guidance for the ambiguous pricing/model parameters.

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 never states a verb or resource — it opens with 'Recorded model 9649 / 09649P,' which is an identifier, not a statement of what the tool does. The actual purpose is only recoverable from the title ('Plan personal-care refill purchases · Wahl Color Pro Rechargeable Clipper Kit'), and the opaque name tds_purchase_d06 carries no signal. An agent reading only the description cannot tell what action is performed or how it differs from the many sibling tds_purchase_m_* 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?

There is no when-to-use guidance, no statement of prerequisites, and no naming of alternatives among the ~30 sibling purchase tools. The sentences present ('use the seller's model field or exact variant name', 'Enter prices in the same currency') are data-entry rules, not selection guidance. An agent must guess whether this tool applies to its task.

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.