Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Bevel Safety Razor

tds_purchase_m_bevel_safety_razor
Read-onlyIdempotent

Recorded model Safety Razor. 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_safety_razor"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 the safety profile is fully covered by structured data. The description adds two useful conventions beyond that: prices must share a currency, and the price should be the amount appearing on the order. However, it never clarifies that despite the "purchase" naming no transaction occurs, nor what the tool computes or 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?

The text is short and free of padding, and the currency/amount conventions are stated compactly. But the opening sentence is a dangling modifier that conveys nothing actionable, and the remaining sentences are a flat list of input rules with no structure prioritizing what matters most.

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 5-required-parameter calculation tool with no output schema, the description does far too little: it explains neither the relationship between alreadyIncluded and totalUnitsNeeded nor what the result represents. Given there are no rich annotations to fall back on regarding what is computed, an agent lacks the information needed to invoke this correctly rather than plausibly.

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 parameter meaning; it addresses only offeredModel and pricePerPack. The three quantity parameters that drive the actual calculation — unitsPerPack, alreadyIncluded, and totalUnitsNeeded — get no explanation at all, leaving the core arithmetic semantics ambiguous. With 5 required params at 0% coverage, this is a substantial shortfall.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 Safety Razor," which identifies the product covered but never states the action the tool performs (planning/recording a purchase quantity). The title supplies "Plan personal-care refill purchases," but an agent reading only the description cannot tell whether this computes a plan, stores a preference, or returns a quote. The model name does distinguish it from the other per-product siblings, so it is not a pure tautology.

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?

"Use the seller's model field or exact variant name" is input-format guidance, not when-to-use guidance. There is no statement of when this tool should be chosen over a sibling product tool (e.g., blades vs. razor), and no preconditions or exclusions are given. An agent must infer applicability purely from the tool name.

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.