Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · quip Sonic Toothbrush

tds_purchase_m_quip_sunset_metal_sonic_toothbrush
Read-onlyIdempotent

Recorded model Sonic Toothbrush. 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_quip_sunset_metal_sonic_toothbrush"
  }
}

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 a safe, idempotent, non-destructive read, so the description only needs to add context. It adds nothing about what the tool computes or returns, and given the 'purchase' name, an agent could easily assume it places an order; the description never clarifies that it does not.

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?

Four short sentences with no padding, so it is compact. But the opening line is a dead sentence and the remaining guidance is fragmented into imperatives with no framing of the operation as a whole.

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?

Five required parameters with zero schema descriptions and no output schema is a heavy burden for a description to carry. With three of the five inputs unexplained and no statement of what the tool produces, an agent cannot reliably fill in the call.

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 must compensate for all five parameters and doesn't. It clarifies offeredModel (seller's model field or exact variant name) and gives currency guidance for pricePerPack, but leaves unitsPerPack, alreadyIncluded, and totalUnitsNeeded entirely 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 opens with 'Recorded model Sonic Toothbrush', which restates the product name rather than stating a verb or an action. It never says that the tool records a refill purchase plan, computes pack counts, or writes anything anywhere; the title carries the only hint of intent.

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?

Three of the four sentences are field-entry advice ('use the seller's model field', 'enter prices in the same currency', 'use the amount that will appear on the order'), not when-to-use guidance. Nothing says when this planning tool applies versus the quoting siblings, nor what prerequisites must be true before calling it.

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.