Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Tangle Teezer Compact Styler

tds_purchase_m_tangle_teezer_compact_styler
Read-onlyIdempotent

Recorded model Compact Styler. 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_compact_styler"
  }
}

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=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered without the description. The description adds useful validity constraints (prices in a single currency, use the amount that will appear on the order) but never explains what the tool does with the numbers or what it returns, which matters since no output schema exists.

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 four sentences are short and the actionable parameter rules come early, but the leading sentence ("Recorded model Compact Styler") carries no information and occupies the most valuable front-loaded position. Nothing is padded beyond that, but the structure spends its opening on a restatement.

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-required-parameter computation tool with no output schema and no parameter descriptions, the definition is not complete enough: the relationship between alreadyIncluded and totalUnitsNeeded, and the meaning of unitsPerPack, are left entirely to inference. An agent would have to guess at the quantity semantics before it could 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% across five required parameters, so the description carries the full burden. 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, leaving the core quantity logic 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 first sentence, "Recorded model Compact Styler," only restates the tool name/title and never states an action verb or what the tool produces. An agent cannot tell from the description whether this records a purchase, computes a needed quantity, or returns a quote, and nothing distinguishes it from the many sibling per-product 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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The instructions that do exist ("use the seller's model field or exact variant name") are data-entry rules for one parameter, not selection guidance.

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.