Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Tangle Teezer The Original Fine & Fragile

tds_purchase_m_tangle_teezer_fine_fragile
Read-onlyIdempotent

Recorded model The Original Fine & Fragile. 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_tangle_teezer_fine_fragile"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context — prices must share one currency and must be the amount that appears on the order (implying no currency conversion). It does not disclose what the tool computes or returns, which for a planning tool is a notable gap.

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 padding, but the leading sentence is redundant with the title and pushes the only actionable guidance (currency, order amount) to the back. Reasonably tight but not front-loaded with purpose.

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?

A five-parameter, all-required computation tool with no output schema and zero schema coverage needs the description to explain the quantity math (packs × unitsPerPack vs alreadyIncluded vs totalUnitsNeeded). Only input-formatting hints are given, leaving the tool's central semantics undocumented.

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 five parameters. It clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (same currency, order amount), but says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded — the core inputs of the planning calculation.

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 The Original Fine & Fragile," which merely restates the title/product name rather than stating the action (planning or computing a refill purchase quantity). An agent cannot tell from the description what the tool actually does, only which product it concerns.

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 when-to-use or when-not-to-use guidance, and no mention of how this differs from the many sibling tds_purchase_m_* product tools. The only guidance ("Use the seller's model field or exact variant name") is about filling a parameter, not about selecting the tool.

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.