Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Cocolab Kids Cocobrush

tds_purchase_m_cocolab_kids_cocobrush
Read-onlyIdempotent

Recorded model Kids 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_kids_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 structurally. The description adds nothing beyond that: no mention of what the tool returns, whether it writes a plan, or what happens to quantities already supplied. It does not contradict the annotations.

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?

Four short sentences with no filler, so there is little waste. However, the lead sentence is a non-informative identifier rather than a front-loaded statement of purpose, so the structure spends its most prominent position on the least useful content.

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?

This is a five-required-parameter planning tool with zero schema coverage and no output schema, so the description carries the full explanatory burden — and it does not meet it. Nothing explains how alreadyIncluded interacts with totalUnitsNeeded to derive a purchase quantity, which is the core logic an agent would need to call this correctly.

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%, so the description must carry all parameter meaning, and it only touches two of five: offeredModel (use the seller's model field or exact variant name) and pricePerPack (same currency, amount as it appears on the order). The key planning inputs — unitsPerPack, alreadyIncluded, and totalUnitsNeeded — are never explained, leaving the arithmetic relationship among them entirely undocumented.

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 description opens with "Recorded model Kids Cocobrush," which merely restates the product identity already in the tool name/title rather than stating what operation is performed. The actual action (planning refill purchase quantities for this variant) is only inferable from the title, not from the description body.

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 sentences "Use the seller's model field or exact variant name" and "Use the amount that will appear on the order" are input-formatting hints, not when-to-use guidance. There is no statement of when this planning tool applies versus the many sibling purchase tools, and no preconditions 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.