Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Remington Smooth & Silky Facial Epilator

tds_purchase_d08
Read-onlyIdempotent

Recorded model EP1050FCDN. 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_d08"
  }
}

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 readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds only a price-selection rule ("Use the amount that will appear on the order") and does not clarify that this is a planning/recording operation, what is produced, how alreadyIncluded vs totalUnitsNeeded is reconciled, or what happens on repeat calls beyond the idempotent hint.

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 free of filler, but it reads as four disconnected fragments rather than a structured explanation. Leading with an opaque model string ("Recorded model EP1050FCDN") spends the most prominent position on a value rather than on what the tool does.

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, no output schema, and zero schema-level descriptions, the definition needs to be self-sufficient and is not. An agent cannot tell from this text what the tool returns (a plan? a cost? a record?) or how the two quantity parameters interact, which is essential for correct invocation.

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 explanatory burden and does not. It addresses only offeredModel loosely ("use the seller's model field or exact variant name") and pricePerPack's currency, while unitsPerPack, alreadyIncluded, and totalUnitsNeeded — which determine the computed order quantity — 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 — no verb, no object, no mention of planning, quoting, or computing a refill purchase. Its first sentence, "Recorded model EP1050FCDN," is a data hint rather than a purpose statement, and an agent must fall back on the title and tool name to infer intent. It does not distinguish this tool from the roughly 30 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 when-to-use, when-not-to-use, or alternative-tool guidance at all, which is a notable gap given the dense sibling cluster (tds_purchase_a03–a25, b01–b07, quote tools). The only directives are input-formatting rules ("Use the seller's model field or exact variant name", currency consistency), which are data-entry conventions, not invocation 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.