Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Bevel Trimmer SE

tds_purchase_m_bevel_trimmer_se
Read-onlyIdempotent

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

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, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds two useful behavioral constraints (use one currency, enter the amount that will appear on the order), but it never discloses what the tool actually computes or returns for a planning/purchase task.

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?

Three short sentences with no bloat, but the leading sentence is wasted on restating the model name instead of front-loading the actual function. The remaining two sentences are efficient constraints.

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?

With five required parameters, zero schema documentation, and no output schema, the definition should explain how the inputs combine (packs vs. units, already-included offset) and what the result represents. Instead it addresses only model naming and currency, leaving an agent to guess at the core calculation.

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 carries full burden, yet it only clarifies two of five parameters: offeredModel (seller's model field or exact variant name) and pricePerPack (currency consistency, order amount). unitsPerPack, alreadyIncluded and totalUnitsNeeded get no explanation, and the relationship between alreadyIncluded and totalUnitsNeeded is left ambiguous.

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 "Recorded model Trimmer SE," which merely restates the name and title rather than stating an action. Only the title ("Plan personal-care refill purchases") suggests the operation, so the description itself gives no verb describing what the tool computes or produces.

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 indication of when to pick this tool over siblings such as tds_purchase_m_bevel_trimmer or tds_purchase_m_bevel_blades, nor any prerequisite or exclusion. The guidance present (currency consistency, order amount) is about data entry, not tool selection.

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.