Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · quip Ultra Lite Stand

tds_purchase_m_quip_white_ultra_lite_stand
Read-onlyIdempotent

Recorded model Ultra Lite 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_lite_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
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 a closed world, so safety is covered. The description adds nothing about behavior beyond that: it does not say whether a plan line is persisted, what happens on duplicate submissions, whether values are validated or clamped, or how units are reconciled.

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?

It is short and front-loads the model constraint, but the opening fragment "Recorded model Ultra Lite Stand" earns no place since it merely echoes the title. The remaining two clauses are useful and compact, so there is little waste beyond that first sentence.

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 parameters, no output schema and zero schema coverage, the description should explain each input and what the operation produces. It covers roughly two of five parameters and gives no indication of the result, making it under-specified for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 load; it partially does. It explains offeredModel (use the seller's model field or exact variant name) and pricePerPack (same currency, amount that will appear on the order), but leaves unitsPerPack, alreadyIncluded and totalUnitsNeeded entirely unexplained despite all five being required.

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 Ultra Lite Stand" restates the tool name and title without a clear verb telling the agent what action is performed (e.g. record a purchase-plan line for this model). It names the resource but gives no differentiation from the many sibling product variants, and the only real content is about how to fill in fields.

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 when-to-use, when-not-to-use, or alternative-selection guidance; the description never explains how this differs from sibling purchase-plan tools or from the quote/planning siblings. "Use the seller's model field or exact variant name" is input formatting advice rather than 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.