Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Cocolab Cocobrush

tds_purchase_m_cocolab_cocobrush
Read-onlyIdempotent

Recorded model Cocobrush. 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_cocobrush"
  }
}

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 elsewhere. The description adds nothing on top of that: it says nothing about what gets computed or returned, whether planning affects a real order, or how the numbers are reconciled — the currency note is input-oriented, not behavioral.

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-loaded with no filler, so there is nothing wasteful to trim. But brevity comes at the cost of intelligibility: the opening fragment "Recorded model Cocobrush" is cryptic and the three sentences read as scattered hints rather than a structured explanation.

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, fully-required tool with zero schema description coverage and no output schema, the description should explain the units/needed math and what the result represents. Instead the three most semantically opaque parameters are undocumented, leaving an agent unable to call it correctly without guessing.

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 coverage is 0% for all five required parameters, so the description must compensate and does so only partially: it clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (same currency as the order). unitsPerPack, alreadyIncluded, and totalUnitsNeeded — the three parameters that actually drive the refill calculation — are left entirely undefined.

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 Cocobrush" identifies the product but never states the action — nothing in the description says the tool purchases, plans, or quotes a refill order. Only the title's "Plan personal-care refill purchases" supplies the verb, and it does not clarify what output is produced; the model name does at least separate it from the kids/other Cocobrush siblings.

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 guidance on when to call this tool versus the many sibling purchase tools or the quote tools. The sentences about currency and "the amount that will appear on the order" are input conventions rather than usage conditions, and no prerequisites or exclusions are given.

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.