Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Tangle Teezer The Ultimate Detangler

tds_purchase_d16
Read-onlyIdempotent

Recorded model The Ultimate Detangler. 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_d16"
  }
}

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond that: it never says whether a result is computed and returned, whether anything is persisted, or what the 'plan' looks like. The phrase "Recorded model" is ambiguous enough to be misread as a write operation, though it does not strictly contradict the read-only 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?

The text is short with no filler, but it is structured as a sentence fragment followed by three disconnected imperative rules. It is compact rather than front-loaded, since the one sentence that could orient the agent (the tool's purpose) is missing entirely.

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?

Five required parameters, no output schema, no annotation-derived semantics, and no schema descriptions make this a case where the description should explain the computation and return shape. Instead it covers only naming and currency conventions, leaving an agent unable to predict what the tool returns or how alreadyIncluded and totalUnitsNeeded combine.

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 load and it largely does not. It clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (same currency as the order), but says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded — the three fields whose interaction (how many units are already owned vs. how many are needed) is the core semantics of a refill planner.

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 the fragment "Recorded model The Ultimate Detangler," which identifies the product but never states a verb or what the tool actually produces. The action ('plan personal-care refill purchases') only appears in the title, so an agent reading the description alone cannot tell whether this computes a buy quantity, records a purchase, or returns a plan.

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?

All guidance is about filling in fields (use the seller's model string, keep currency consistent, use the order-visible amount) rather than when to select this tool. With 30+ sibling purchase tools, there is no statement of how this differs from e.g. tds_purchase_a03 or the other Tangle Teezer variants, nor any prerequisite or exclusion.

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.