Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Bevel Trimmer

tds_purchase_m_bevel_trimmer
Read-onlyIdempotent

Recorded model Trimmer. 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_trimmer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds nothing beyond that: it does not say what the tool computes from unitsPerPack/alreadyIncluded/totalUnitsNeeded, whether results are persisted, or what the caller receives back. "Recorded model" is also ambiguous enough to invite a write interpretation that the annotations do not support.

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?

Short and mostly front-loaded, with each formatting hint in its own sentence. However, the opening fragment "Recorded model Trimmer" is unclear filler that occupies the position where the purpose statement should be, so space is spent without conveying meaning.

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, zero-coverage, no-output-schema planning tool, the description is too thin: it never explains the relationship between alreadyIncluded and totalUnitsNeeded (the core of a refill plan) or what the result represents. An agent could format the inputs correctly but still not know what the call actually produces.

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 and largely fails. It clarifies offeredModel (seller's model field or exact variant name) and pricePerPack (same currency as the order), but leaves unitsPerPack, alreadyIncluded, and totalUnitsNeeded — the fields that actually drive the planning calculation — entirely unexplained.

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 Trimmer" essentially restates the tool name/title without stating a verb or the operation performed (recording a purchase? planning quantities? returning a computed refill count?). A reader cannot tell from the description alone whether this writes a purchase entry or computes units needed from the numeric fields.

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: nothing explains when to pick this Bevel Trimmer entry over siblings like the trimmer_se variant, the battery, or blades, nor what preconditions apply. The only directives are input-formatting tips (use the seller's model field, keep currency consistent), which are 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.