Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Cocolab Kids Reflosser

tds_purchase_m_cocolab_kids_reflosser
Read-onlyIdempotent

Recorded model Kids Reflosser. 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_reflosser"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 closed-world scope, so the safety profile is free. The description adds real behavioral context on pricing input ('same currency', 'amount that will appear on the order'), which is useful for avoiding mismatched inputs, but says nothing about what is produced or how the quantities 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler, and the model-identification constraint is front-loaded. The opening clause is awkwardly worded but nothing is redundant.

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 5-parameter, all-required planning tool with no output schema and no parameter descriptions, the description should explain how alreadyIncluded offsets totalUnitsNeeded and what unitsPerPack means. It covers only two of the five inputs, leaving an agent to guess the semantics of the core refill computation.

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 clarifies offeredModel (seller's model field / exact variant name) and pricePerPack (currency consistency, order-visible amount), but leaves unitsPerPack, alreadyIncluded, and totalUnitsNeeded entirely unexplained — including how the last two interact, which is the core calculation.

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 identifies the exact product variant ('Kids Reflosser') and pins it to the seller's model field, which is the main differentiator among the many SKU-specific purchase siblings. However, it never states a verb or outcome — 'Recorded model Kids Reflosser' reads as a data label rather than saying what the tool does (plan/record a purchase for this SKU).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is implicit usage guidance: use the seller's model field or exact variant name, and enter the price that will appear on the order. But there is no explicit when-to-use vs. when-not, no mention of the quote-based siblings (tds_quote_framing_plan, tds_quote_shelf_care), and no prerequisites for invoking it.

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.