Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · quip Rev Stand

tds_purchase_m_quip_white_rev_stand
Read-onlyIdempotent

Recorded model Rev Stand. 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_quip_white_rev_stand"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered and the description is not obliged to restate it. The description does add real domain constraints — use the amount that will appear on the order, keep a single currency — but it never says what the tool produces or why a read-only tool is named "purchase", leaving a gap for a planning/calculation tool with no output schema.

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?

Three short sentences with no padding, but they are not front-loaded: the opening fragment is the least informative part, and the actionable input rules only appear afterward. Brevity here reflects under-specification rather than efficiency.

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?

For a five-parameter required-input tool with no schema descriptions, no output schema, and a large family of near-identical siblings, the definition should explain how the unit counts combine and what the result represents. Neither is present, so an agent could supply valid but semantically wrong values without any signal.

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 burden. It only loosely clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (currency consistency, order amount), and says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded — the three fields whose interaction determines the result.

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 Rev Stand" is a fragment, not a statement of what the tool does — it names the variant but supplies no verb describing the operation (record? compute a refill plan? quote?). The title "Plan personal-care refill purchases" carries the actual purpose, and the description never confirms or elaborates it, so an agent cannot tell this apart from the many sibling stand variants beyond the model name.

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 only guidance is input-format related ("Use the seller's model field or exact variant name", "Enter prices in the same currency"). There is no statement of when this tool should be chosen over the adjacent quip stand variants (ultra_lite_stand, ultra_stand, rev_mirror_mount) or how planning differs from an actual order, leaving selection to guesswork.

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.