Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Cocolab Great Gums Brush

tds_purchase_m_cocolab_great_gums_brush
Read-onlyIdempotent

Recorded model Great Gums Brush. 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_cocolab_great_gums_brush"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/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 safety and repeatability are covered and the description does not contradict them. The description adds two genuine behavioral rules beyond the annotations: prices must be in a single consistent currency, and the price should be the amount that will appear on the order (not list price or pre-discount price). It does not say what is recorded or returned, so it stops short of full transparency.

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 filler, but the structure is not front-loaded: the opening fragment identifies the product rather than stating what the tool does, and the actionable input rules are appended afterwards. It is compact, yet the space used by the first sentence is largely redundant with the tool name and title.

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?

With five required parameters, zero schema descriptions and no output schema, the definition should explain both the quantity semantics and what the tool produces (a recorded line item, a priced plan entry, an ID?). Instead it covers only currency and price conventions, leaving the core calculation intent — alreadyIncluded vs totalUnitsNeeded — undocumented for a tool whose entire purpose is planning refill quantities.

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 and it only partially does. It clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (same currency, on-order amount), but unitsPerPack, alreadyIncluded and totalUnitsNeeded are left entirely undefined — an agent has no guidance on whether alreadyIncluded is subtracted from totalUnitsNeeded or how the two interact to size the order.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact product ("Recorded model Great Gums Brush"), which pins the resource and distinguishes it from the many sibling product tools. However, it never states the action: "Recorded model ..." is a fragment, not a verb+resource statement, and an agent must infer from the tool name and the price/units parameters that this records a purchase plan for that product. The title carries the actual purpose ("Plan personal-care refill purchases"), not the description.

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 conditional guidance is input-level ("Use the seller's model field or exact variant name"), with no statement of when this tool should be chosen over alternatives such as tds_quote_framing_plan or tds_quote_shelf_care, or whether it belongs inside an existing plan/quote session. Nothing says what to do when the variant does not match or how it relates to the other product-level purchase tools.

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.