Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · quip Rev Travel Case

tds_purchase_m_quip_rev_travel_case
Read-onlyIdempotent

Recorded model Rev Travel Case. 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_rev_travel_case"
  }
}

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, and destructiveHint=false, so the safety profile is covered structurally. The description adds only the currency-consistency rule and "use the amount that will appear on the order," with nothing about what the tool produces, whether it persists a record despite the name "purchase," or how the units math is applied.

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 little waste, and the guidance about model naming and currency is front-loaded. However, the opening sentence spends space restating the product name rather than establishing the action, so brevity here reflects under-specification as much as tight writing.

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 tool with five required numeric/string parameters, no output schema, and no annotation-level explanation of results, the description is far too thin. An agent cannot tell what computation is performed with alreadyIncluded and totalUnitsNeeded or what the response contains, which is precisely the gap the description should fill.

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 does not. It clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (matching currency, order amount) but says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded, which are the parameters that actually determine the computed 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 Travel Case" identifies the product but never states a verb or the operation itself (plan/compute/record a purchase). An agent must read the title to guess that this plans a refill purchase. Against dozens of near-identically named tds_purchase_m_* siblings, the description supplies no distinguishing action.

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?

There is no statement of when to use this tool versus the sibling product tools or the quote/travel tools. The remaining sentences are input formatting advice (use the seller's model field, same currency), not usage routing.

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.