Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Braun Series 9 Pro+ Electric Shaver

tds_purchase_d05
Read-onlyIdempotent

Recorded model 9677cc. 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_d05"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/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 a closed world, so the safety profile is covered. The description adds only that the catalogued model is 9677cc and a currency convention, but says nothing about whether this computes or persists anything, and "Recorded model" is ambiguous enough to confuse a read-only planner.

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 with no filler, but the four sentence fragments are unordered hints rather than a front-loaded purpose statement, so the reader hits model-number trivia before learning what the tool is for.

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 five-parameter, fully-required planning tool with no output schema and no annotations explaining the arithmetic should define the pack/units relationship. The description never explains how unitsPerPack, alreadyIncluded and totalUnitsNeeded combine, so an agent cannot confidently supply them.

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 full burden. It only touches offeredModel (use the seller's model field or exact variant name) and pricePerPack (same currency, amount as shown on the order), leaving unitsPerPack, alreadyIncluded and totalUnitsNeeded completely undefined.

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 opens with "Recorded model 9677cc" rather than a verb+resource statement, so it never says what the tool actually does (plan a refill purchase quantity for this shaver model). Purpose is only inferable from the name and title, which makes it near-tautological for a reader of the body text.

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?

"Use the seller's model field or exact variant name" and "Use the amount that will appear on the order" are input conventions, not when-to-use guidance. Nothing tells the agent when this planning tool applies versus siblings like tds_quote_framing_plan or the item-specific purchase tools.

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.