Skip to main content
Glama

The Doll Scout Home Tools

Plan personal-care refill purchases · Kitsch King Pillowcase - Aura

tds_purchase_m_kitsch_king_pillowcase_aura
Read-onlyIdempotent

Recorded model King Pillowcase - Aura. 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_king_pillowcase_aura"
  }
}

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 the tool read-only, idempotent, non-destructive, and closed-world. The description adds a small amount of behavioral context about matching the seller's model field and using the price that appears on the order, but it does not explain return values, persistence, or validation behavior.

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?

The description is short and front-loads the product identifier before the parameter notes. The opening fragment 'Recorded model King Pillowcase - Aura.' is awkward, but there is little wasted wording overall.

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?

This is a five-parameter planning tool with no schema descriptions and no output schema. The description supplies only partial parameter guidance and omits the meaning of key quantity fields, so it is not complete enough to reliably guide an agent through the required inputs.

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 carry all parameter meaning. It clarifies offeredModel ('use the seller's model field or exact variant name') and says prices must share a currency, but it does not explain unitsPerPack, alreadyIncluded, or totalUnitsNeeded, leaving three of five required parameters undocumented.

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 names the product ('King Pillowcase - Aura') and implies a purchase-planning input, but it never states the action explicitly. The title and tool name carry most of the purpose, leaving the description itself vague about what is planned or recorded.

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 description gives instructions for filling in parameters ('use the seller’s model field', 'enter prices in the same currency'), but no guidance on when to use this tool versus sibling purchase-planning tools or how it relates to them. It also provides no exclusions or prerequisites.

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.