Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · beautyblender Bodyblender

tds_purchase_m_beautyblender_bodyblender_original
Read-onlyIdempotent

Recorded model Bodyblender. 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_beautyblender_bodyblender_original"
  }
}

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds only input-entry constraints and does not explain the tool’s actual behavior, such as whether it computes pack counts or what kind of plan it 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 description is short and contains no obvious filler, but the opening 'Recorded model Bodyblender' is awkward and does not front-load the tool’s purpose. The remaining sentences read as field notes rather than a structured explanation of the tool.

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 parameters, no schema descriptions, and no output schema, the definition is significantly under-specified. An agent can infer the product and a few input constraints, but cannot confidently understand the calculation logic or how alreadyIncluded and totalUnitsNeeded should be interpreted.

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?

With 0% schema description coverage, the description must carry parameter meaning. It partially clarifies offeredModel ('seller’s model field or exact variant name') and pricePerPack currency consistency, but says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded, nor how those values interact.

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 identifies the product ('Recorded model Bodyblender') and gives field-entry hints, but never states the action the tool performs, such as calculating or planning refill purchases. It largely restates the product name without a clear verb+resource statement an agent can use to distinguish its purpose from sibling purchase 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?

It offers parameter-entry advice such as using the seller’s model field, matching currency, and using the order amount, but gives no explicit guidance on when to use this tool versus alternatives or when not to use it. The product-specific name implies selection, but the description itself does not route the agent.

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.