Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · hello classic toothbrush in black

tds_purchase_m_hello_classic_toothbrush_in_black
Read-onlyIdempotent

Recorded model classic toothbrush in black. 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_hello_classic_toothbrush_in_black"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful operational context about how the recorded values will be interpreted ("Enter prices in the same currency", "Use the amount that will appear on the order"), but never clarifies the tension between a "purchase" tool and its read-only, non-executing annotation — i.e., that nothing is actually bought.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the item identity front-loaded and no wasted framing. The phrasing is somewhat boilerplate ("Recorded model …") but each sentence carries usable instruction.

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 five-parameter plan-recording tool with no output schema and zero schema descriptions, the definition should explain the relationship among the four numeric fields and confirm that it records rather than executes a purchase. Neither is present, leaving the agent to guess at both the semantics and the side-effect profile.

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% with five required parameters, so the description must carry the load. It clarifies two of them — offeredModel (seller's model field or exact variant name) and pricePerPack (currency consistency, order amount) — but says nothing about unitsPerPack, alreadyIncluded, or totalUnitsNeeded, including how "already included" units affect how many packs are needed, which is the core arithmetic.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recorded model classic toothbrush in black" names the exact resource and distinguishes this tool from its many sibling product tools, but it is a noun phrase rather than a verb+resource statement of what the tool does. An agent can tell which item it targets but must infer the action (record a purchase/refill plan for this variant) from the name and title.

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?

The only guidance is about data entry ("Use the seller's model field or exact variant name"), not about when to choose this tool over the toothbrush sibling variants or the quote tools. There are no conditions, prerequisites, or exclusions, so the agent is left to infer selection purely from the product name.

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.