Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Real Techniques Makeup Setting Brush

tds_purchase_m_real_techniques_makeup_setting_brush
Read-onlyIdempotent

Recorded model Makeup Setting Brush. 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_makeup_setting_brush"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. What the description fails to disclose is the actual behavior: that this computes a purchase plan from unitsPerPack, alreadyIncluded and totalUnitsNeeded, and what it returns (no output schema exists). Given a name starting with "purchase" and read-only annotations, the description leaves real ambiguity about what is computed versus what is transacted.

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?

Four short, front-loaded sentences with no filler, but the brevity comes from under-specification rather than precision. The space that is used is spent on formatting rules instead of the tool's operation.

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

Completeness1/5

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

For a five-parameter, all-required computation tool with 0% schema coverage and no output schema, the description omits the calculation logic, the meaning of three parameters, and all return information. An agent could not reliably invoke this tool correctly from this definition alone.

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%, so the description must carry the full burden, yet it clarifies only offeredModel and pricePerPack. unitsPerPack, alreadyIncluded and totalUnitsNeeded are entirely undefined, even though these are the core inputs whose meaning (units already on hand versus units still needed) determines the result. "Use the amount that will appear on the order" is also ambiguous about which parameter it governs.

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 opening sentence, "Recorded model Makeup Setting Brush," only restates the product name in the tool title and contains no verb describing what the tool actually does. The real purpose (planning a refill quantity) appears only in the title, not in the description body, so an agent cannot tell from the description what operation it performs.

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?

"Use the seller's model field or exact variant name" and "Use the amount that will appear on the order" are input-formatting hints, not guidance on when to choose this tool over a sibling. Nothing indicates when a refill-planning call is appropriate, nor how it relates to the many other brush variants listed.

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.