Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Real Techniques Makeupsaver Sponge

tds_purchase_m_real_techniques_makeupsaver_sponge
Read-onlyIdempotent

Recorded model Makeupsaver Sponge. 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_makeupsaver_sponge"
  }
}

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=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds the currency-consistency constraint and "Use the amount that will appear on the order," but the phrase "Recorded model" sits awkwardly against a read-only tool and it never explains what the tool produces or whether an existing entry is overwritten or merged. It adds some context but leaves the core behavior opaque.

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 sentences with no filler, but the opening sentence carries no actionable information and the remaining guidance is unordered rather than front-loaded by importance. It is concise in length yet not well organized: nothing signals that the three unit-count fields are the ones an agent must reason about.

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?

A tool with five required numeric/string parameters, zero schema coverage, no output schema, and only generic annotations needs the description to explain the counting logic (units per pack, already-included units, total needed) and the result. The description never does, so an agent has to guess at the relationship between alreadyIncluded and totalUnitsNeeded.

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% — none of the five required parameters has a description. The text only partially compensates: "seller's model field or exact variant name" maps to offeredModel, "same currency" maps to pricePerPack, but unitsPerPack, alreadyIncluded, and totalUnitsNeeded (the keys that actually determine the computation) are never explained. "Use the amount that will appear on the order" is ambiguous about which of the three count fields 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 Makeupsaver Sponge" restates the product identity already encoded in the name and title; it never states the action the tool performs (recording a purchase/refill plan line, computing a quantity, etc.). An agent cannot tell from the description whether this creates a plan entry, validates a SKU, or returns a quote, only which product it concerns.

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 "Use the seller's model field or exact variant name" and "Enter prices in the same currency" are input-formatting instructions, not when-to-use guidance. Nothing says how this differs from the ~30 sibling product purchase tools (which product line, which variant of the sponge) or when an agent should pick this one over them.

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.