Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Tangle Teezer The Original

tds_purchase_m_tangle_teezer_the_original
Read-onlyIdempotent

Recorded model The Original. 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_the_original"
  }
}

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 closed-world, so the safety profile is covered without the description's help. The description adds a useful constraint, "Use the amount that will appear on the order," clarifying the source of the figures rather than leaving the agent to guess. It says nothing about what is stored, what is returned, or whether re-invoking with the same model overwrites prior entries.

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, which is appropriately sized. However, the lead sentence is a cryptic noun phrase rather than a statement of the tool's action, so the most important information is neither front-loaded nor clearly expressed.

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 all-required tool with no schema descriptions and no output schema, the description omits the core semantics of three parameters and never states the operation being performed. Annotations cover safety but cannot compensate for the missing meaning of the unit-count fields.

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, so the description carries full burden. It explains only offeredModel (match the seller's model field or exact variant name) and part of pricePerPack (currency consistency), leaving unitsPerPack, alreadyIncluded and totalUnitsNeeded entirely undefined. The distinction between units already included and total units needed is exactly the ambiguity an agent cannot resolve from a bare integer schema.

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 The Original" is a fragment that restates the title rather than stating an action; it never says it records or plans a purchase line for this product. The verb is only inferable from the tool name prefix, not from the description itself. Only the model identity is disambiguated from the many sibling variants.

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?

Provides data-entry rules (use the seller's model field or exact variant name; prices in one currency) but no when-to-use vs when-not guidance and no reference to any sibling. Nothing tells the agent how this differs from the other Tangle Teezer variant tools beyond the model name matching task.

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.