Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Real Techniques Everything Blending Duo

tds_purchase_m_real_techniques_everything_blending_3620891b
Read-onlyIdempotent

Recorded model Everything Blending Duo. 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_m_real_techniques_everything_blending_3620891b"
  }
}

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, closed-world, so the safety bar is low, yet the description adds no behavior beyond that. It does not say whether anything is persisted, what the tool computes (a coverage/quantity plan), or what happens when alreadyIncluded exceeds totalUnitsNeeded.

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 front-loaded with the model name, with no filler sentences. But brevity here is under-specification rather than efficiency, since the space that could explain the quantity logic is unused.

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 at 0% schema coverage and no output schema, the description should explain the pack/quantity arithmetic and the meaning of alreadyIncluded. It leaves the core computation opaque, so an agent cannot reliably fill the fields.

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 coverage is 0%, so the description must carry all five parameters, but it only gestures at offeredModel and pricePerPack. unitsPerPack, alreadyIncluded, and totalUnitsNeeded are never defined, and "use the amount that will appear on the order" is ambiguous about which quantity field it refers to.

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?

"Recorded model Everything Blending Duo" restates the product name rather than stating a verb+resource; the agent must infer from the title that this plans/records a refill purchase. It never says what the tool actually does with the five inputs.

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?

The sentences are field-entry hints ("use the seller's model field", "enter prices in the same currency") rather than when-to-use vs. when-not guidance. Nothing explains when to pick this product-specific tool over a sibling or a generic quote tool.

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.