Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Bevel Shave Brush

tds_purchase_m_bevel_shave_brush
Read-onlyIdempotent

Recorded model Shave Brush. 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_shave_brush"
  }
}

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 and destructiveHint=false, so the agent knows the safety profile. The description adds useful data-entry constraints (exact variant naming, single currency, use the on-order amount) but never clarifies whether the tool persists anything or simply derives a plan, leaving the word "Recorded" ambiguous against the read-only annotation.

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 definition is short and front-loaded with no wasted clauses, but the lead sentence is the least informative part, and the remaining tips are undifferentiated fragments rather than a structured explanation of purpose then parameters.

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 numeric/string inputs, no output schema, and no enum or nested structure, the description should explain how alreadyIncluded and totalUnitsNeeded interact with unitsPerPack and pricePerPack. It leaves three of five parameters and the tool's actual output undefined.

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 five required parameters, so the description carries the full burden. It gives meaning for only two of them (offeredModel via "seller's model field or exact variant name," pricePerPack via "same currency"), and says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded, whose roles in deriving the purchase quantity remain opaque.

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 Shave Brush," which restates the product name in the title rather than stating an operation. There is no verb telling the agent whether the tool records a purchase plan, computes pack quantities, or quotes a price, so it is hard to distinguish 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?

Sentences like "Use the seller's model field or exact variant name" and "Enter prices in the same currency" are data-entry tips, not when-to-use guidance. Nothing says when this tool should be chosen over the sibling purchase or quote tools, nor what inputs are 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.