Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Waterpik Aquarius Water Flosser

tds_purchase_d03
Read-onlyIdempotent

Recorded model WP-660. 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_d03"
  }
}

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, idempotentHint and non-destructive, so the safety profile is covered. The description adds nothing beyond that: it does not say whether this creates a purchase plan, computes pack counts, or how alreadyIncluded interacts with totalUnitsNeeded. The sentence "Recorded model WP-660" hints at recording behavior without explaining it.

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 and has no filler, but it is a sequence of disconnected imperative fragments with no leading statement of purpose. The most product-identifying fact (WP-660) is front-loaded, yet the reader never learns what the call produces.

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?

For a 5-parameter, all-required tool with no output schema and zero schema descriptions, the definition is under-specified on three of five inputs and says nothing about the arithmetic relationship between alreadyIncluded and totalUnitsNeeded. What it does cover — model identity and price conventions — is genuinely useful and correct, so it is not inadequate, just partial.

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 5 required parameters, so the description must compensate and largely does not. It clarifies offeredModel (use the seller's model field or exact variant name) and pricePerPack (same currency, amount as on the order), but unitsPerPack, alreadyIncluded and totalUnitsNeeded — the three fields that determine any computed quantity — receive no explanation at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 as a verb+resource; the only purpose signal comes from the title ("Plan personal-care refill purchases"). The body is entirely a set of input-entry hints ("Recorded model WP-660", "Enter prices in the same currency"), so an agent must infer the operation from the name and title. It is inferable, but not stated.

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 or when-not-to-use guidance, and no mention of the many sibling tds_purchase_* tools that cover other products. The only conditional instruction is about which model string to supply, which is input hygiene rather than routing 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.