Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Cocolab Home & Away Floss Set

tds_purchase_m_cocolab_home_away_floss_set
Read-onlyIdempotent

Recorded model Home & Away Floss Set. 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_home_away_floss_set"
  }
}

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?

The annotations already declare this read-only, idempotent, and non-destructive, so the safety profile is covered. Beyond that, the description does not explain what the tool actually records or computes, what the result represents, or how the required purchase-planning fields interact.

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?

The description is short and mostly imperative, with no wasted filler. However, the opening sentence is ambiguous and does not front-load the tool’s actual purpose, which weakens structure despite the brevity.

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 fields, no output schema, and no parameter descriptions, the definition is too thin. It supplies a few data-entry constraints but omits how the core inputs should be chosen and what the tool returns or records.

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% and there are five required parameters. The description partially clarifies offeredModel and pricePerPack (currency consistency), but it leaves unitsPerPack, alreadyIncluded, and totalUnitsNeeded undefined, so it does not compensate for the missing schema documentation.

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 names the product ("Home & Away Floss Set") but does not state a clear action such as planning, recording, or calculating a purchase. The title helps, but the description itself is closer to a label than a purpose statement and does not distinguish this tool from sibling product-specific purchase tools.

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?

It gives input-entry rules about using the seller’s model field, exact variant name, and consistent currency, but it does not say when to use this tool versus siblings or alternatives. No exclusions, prerequisites, or selection context are provided.

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.