Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Tangle Teezer Hair Pick

tds_purchase_m_tangle_teezer_hair_pick
Read-onlyIdempotent

Recorded model Hair Pick. 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_hair_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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, so safety is covered; the description does not contradict that, and the "plan" framing is consistent with a read-only calculation. It adds some useful operational context — prices must share a currency and match the order amount — but says nothing about what the tool returns or how alreadyIncluded/totalUnitsNeeded affect the result.

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 short imperative sentences with no filler and actionable constraints up front. The opening "Recorded model Hair Pick." is the weakest line, since it conveys no operational information, but the rest is tight.

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?

This is a five-required-parameter tool with 0% schema coverage and no output schema, so the description carries full explanatory weight — yet it explains only two parameters and never describes the refill-planning computation (e.g., how already-included units offset the total needed). An agent could supply plausible but wrong values for half the inputs.

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 must carry the burden. It clarifies only offeredModel (seller's model field or exact variant name) and pricePerPack (same currency, order amount); unitsPerPack, alreadyIncluded, and totalUnitsNeeded are left completely undefined in both schema and description.

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 Hair Pick" largely restates the product name in the tool title rather than naming an operation; there is no verb describing what is actually done (record a plan? compute a refill quantity?). It gives no basis for distinguishing this tool from the dozens of sibling tds_purchase_m_* entries beyond the product name.

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?

The instructions ("Use the seller's model field or exact variant name", "Enter prices in the same currency") are parameter-entry rules, not when-to-use guidance. Nothing says when this purchase-planning tool applies versus a quote or framing/shelf-care sibling, and there are no exclusions or prerequisites.

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.