Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Cricut Joy Xtra Cutting Machine

tds_purchase_d17
Read-onlyIdempotent

Recorded model Joy Xtra / 2010313. Use the seller’s model field or exact variant name. Use one consistent unit for the material and checked values for the exact pack or accessory.

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>",
      "projects": "<projects>",
      "amountPerProject": "<amountPerProject>",
      "unitsPerPack": "<unitsPerPack>",
      "sparePercent": "<sparePercent>"
    },
    "name": "tds_purchase_d17"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only two operational constraints (consistent unit, checked pack/accessory values) and says nothing about what the tool computes, returns, or validates, so it contributes little behavior beyond the structured hints.

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?

Three short sentences with no filler, which is appropriately sized. However, the ordering buries the actual operation behind an identifier string, and the terseness produces ambiguity rather than density.

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?

A five-required-parameter planning tool with no output schema and no documented parameter meanings needs far more than three fragments. An agent cannot determine from this text how sparePercent interacts with amountPerProject and projects, or what result is produced, making correct invocation largely guesswork.

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 all five required parameters, so the description carries the full burden. It partially covers offeredModel (use the seller's model field or exact variant name) and loosely gestures at unit consistency for amountPerProject/unitsPerPack, but 'projects' and 'sparePercent' are never explained, and the pack/accessory sentence is ambiguous about which field it governs.

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 the operation being performed. It gives a recorded model identity ('Joy Xtra / 2010313') and field-level hints, but no verb or outcome such as computing a purchase quantity, so an agent must infer the purpose from the title alone. It does at least distinguish the target item from the many other tds_purchase_* siblings by naming the exact model variant.

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 input guidance, not when-to-use guidance. Nothing tells the agent when to pick this tool over tds_quote_framing_plan, tds_spare_parts_review, or any of the sibling purchase tools, nor what preconditions must hold.

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.