Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · quip Ultra Stand

tds_purchase_m_quip_white_ultra_stand
Read-onlyIdempotent

Recorded model Ultra 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_ultra_stand"
  }
}

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, and openWorldHint=false, so the safety profile is covered. The description adds only the currency-consistency constraint and "the amount that will appear on the order," which hints at order-entry behavior without clarifying what is persisted or returned — mildly at odds with the read-only annotation, though not explicit enough to be a contradiction.

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?

The description is short and uses imperative sentences, but the opening sentence is dead weight and the remaining sentences are an unordered list of constraints with no lead-in stating the tool's job. It is compact but not front-loaded around purpose.

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 five-required-parameter planning tool with no output schema, no schema descriptions, and no enum constraints needs the description to explain the relationship between unitsPerPack, alreadyIncluded, and totalUnitsNeeded. That relationship — the core of the tool — is entirely absent, leaving an agent unable to call it correctly from the 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% across 5 required parameters, so the description must carry the full burden. It explains offeredModel (seller's model field or exact variant name) and constrains pricePerPack (same currency, amount as it appears on the order), but unitsPerPack, alreadyIncluded, and totalUnitsNeeded — the parameters that define the actual computation — get no explanation at all.

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 first sentence, "Recorded model Ultra Stand," merely echoes the name and title without a verb or resource; an agent learns only that this concerns a specific quip stand variant. It never says whether the tool records a purchase, computes pack quantities, or plans refills, so it is largely tautological against the title.

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 routing hint is "Use the seller's model field or exact variant name," which is parameter guidance rather than when-to-use guidance. Nothing distinguishes this from the many near-identical variant siblings (ultra_lite_stand, rev_stand) or states prerequisites, exclusions, or alternatives.

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.