Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Bevel Razor Blades

tds_purchase_m_bevel_blades
Read-onlyIdempotent

Recorded model Razor Blades. 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_bevel_blades"
  }
}

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 openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds only input conventions (currency matching, the amount that will appear on the order) and no behavioral context such as what gets stored, whether re-invocation overwrites prior figures, or what a successful call returns.

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?

It is short and the actionable input rules come early, so nothing drags. But the opening sentence is a non-informative fragment and the remaining sentences are unlabeled imperatives with no structure, so brevity comes at the cost of usefulness rather than from efficiency.

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, entirely undocumented parameters, no output schema and a purchase-planning purpose, the description is far too thin. It should at minimum define how alreadyIncluded and totalUnitsNeeded interact and what a returned plan looks like, and it currently leaves the agent guessing on both.

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% for all five required parameters, so the description carries the full burden, yet it only gestures at offeredModel (seller's model field or exact variant name) and pricePerPack (same currency, amount as on the order). The three quantity parameters unitsPerPack, alreadyIncluded and totalUnitsNeeded are never explained, leaving the most consequential inputs, which drive the computed refill need, 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 description opens with the fragment "Recorded model Razor Blades," which essentially restates the title and never states a verb or what the tool actually does with the supplied figures. An agent cannot tell from this text whether it records a planned purchase, prices out a refill, or validates a selection, and nothing distinguishes it from the many sibling tds_purchase_m_* 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 guidance and no mention of alternatives; only in-field input rules (use the seller's model field or exact variant name, keep currency consistent). Those rules help fill the form but do not tell the agent when this tool is the right choice versus a quote or other purchase sibling.

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.