Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Kitsch Black Detangling Brush

tds_purchase_m_kitsch_detangling_brush_1pc_black
Read-onlyIdempotent

Recorded model Black Detangling 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_kitsch_detangling_brush_1pc_black"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
pricePerPackYes
unitsPerPackYes
alreadyIncludedYes
totalUnitsNeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 and a closed world, so the safety profile is fully covered structurally. The description adds a little operational context — currency consistency and using the amount that will appear on the order — but says nothing about what is recorded, whether re-submitting the same variant overwrites or duplicates, or how the plan aggregates units.

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?

It is short and front-loaded, but the opening sentence ("Recorded model Black Detangling Brush.") is a dangling fragment that spends space without conveying an action, and the remaining sentences are loosely related imperatives rather than an ordered structure.

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?

With five required parameters, no schema descriptions, and no output schema, the description is too thin for the tool's complexity. Three of five inputs receive no explanation, and there is no indication of what the call returns or how the recorded plan is later consumed.

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 burden. It clarifies only offeredModel and pricePerPack; unitsPerPack, alreadyIncluded and totalUnitsNeeded — the semantically riskiest fields, especially whether totalUnitsNeeded is gross or net of alreadyIncluded — are left entirely undefined.

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?

The description identifies the specific product variant ("Recorded model Black Detangling Brush") and the title supplies the action (planning personal-care refill purchases), but the description itself is a fragment with no verb and never states that this tool records a purchase-plan entry. An agent can infer purpose from the name/title pairing but not from the description text 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?

"Use the seller's model field or exact variant name" is guidance about how to fill one parameter, not when to select this tool. There is no statement of when to use this versus the many sibling purchase-plan tools (e.g., other Kitsch variants) or versus the quote tools, and no prerequisites or exclusions are given.

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.