Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Philips Sonicare 4100 Series

tds_purchase_d01
Read-onlyIdempotent

Recorded model HX3681/23. 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_d01"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/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 structurally. The description adds only that prices should be in a consistent currency and reflect the order amount — it says nothing about what is recorded, whether repeated calls accumulate or overwrite, or what the agent gets back.

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?

The description is short with no filler, and each sentence carries content. However it is not front-loaded: it opens with a model number rather than stating the tool's action, so the reader has no frame for the parameter rules that follow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five required parameters, no output schema and only a bare annotations block, the description is too thin for the tool's complexity. It omits the tool's action and three of five parameters, though the two it does explain (model identity and price basis) are the ones most likely to be mis-entered.

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 semantic load, but it only clarifies two of them: offeredModel (seller's model field or exact variant name) and pricePerPack (currency consistency, order amount). unitsPerPack, alreadyIncluded and totalUnitsNeeded — including the distinction between already-included and total-needed units — are left entirely unexplained.

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 what the tool does — there is no verb describing the operation, only a recorded model identifier (HX3681/23) and formatting rules. An agent must infer from the tool name and title that this plans or records a refill purchase, and the description offers no differentiation from the many sibling tds_purchase_* 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 guidance on when to use this tool versus the dozens of sibling purchase tools, nor any prerequisite or exclusion stated. The only conditional advice is about which model string to supply ('seller's model field or exact variant name'), which is parameter guidance rather than usage guidance.

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.