Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Microplane Colossal Foot File

tds_purchase_d12
Read-onlyIdempotent

Recorded model 70903-1PK. 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_d12"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/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 the safety profile is covered; the description should add price/currency and computation semantics on top. It adds only two thin hints (same-currency prices, amount as it appears on the order) and says nothing about what the tool computes, whether results are stored, or what the relationship between alreadyIncluded and totalUnitsNeeded does to the outcome.

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 with no filler, but it is not front-loaded: the least informative sentence (a model number) comes first and the most useful constraint (currency) comes third. Brevity here reflects under-specification rather than disciplined structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Relative to a five-parameter, output-schema-less tool with annotations covering safety, the definition should explain the computation and remaining inputs; it leaves the core semantics (what is calculated from these five numbers) undocumented, which is a real gap for a tool whose whole value is that 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% across five required parameters, so the description must carry the full explanatory burden. It clarifies offeredModel and partially clarifies pricePerPack, but unitsPerPack, alreadyIncluded, and totalUnitsNeeded receive no explanation at all, leaving the actual planning arithmetic undefined.

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 never states what the tool does with the five inputs; it opens with an opaque product identifier ("Recorded model 70903-1PK") and reads as field-level guidance rather than a purpose statement. Only the title hints that this plans a personal-care refill purchase, so an agent must infer the operation from the name and title alone.

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 or when-not-to-use guidance, and no mention of how this differs from the many sibling tds_purchase_* tools. The instructions given ("Use the seller's model field or exact variant name") constrain one input but do not help select the tool.

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.