Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Altenew Snowman Stamp Set

tds_purchase_m_altenew_snowman_stamp_set
Read-onlyIdempotent

Recorded model Snowman Stamp Set. 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_m_altenew_snowman_stamp_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description needed only to add computational context. It adds none: no explanation of how packs are derived from projects/amount/units, how sparePercent rounds up, or what the result contains. The phrase 'Recorded model' is also ambiguous about whether anything is persisted.

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 padding, which is good, but the first sentence is spent on product identification and the remaining two are cryptic fragments. The content is front-loaded but the ordering puts the least informative sentence first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter calculator with no schema descriptions and no output schema, the description should explain the inputs and the resulting quantities. It covers roughly half the parameters only loosely and gives no sense of the returned plan, leaving real gaps despite the tool's modest complexity.

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 numeric/string parameters, so the description carries the full burden. It clarifies offeredModel (seller model field or exact variant name) and implies consistent units for amountPerProject and unitsPerPack, but says nothing about 'projects' or 'sparePercent', the two parameters most likely to be misentered.

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 Snowman Stamp Set', which restates the product name from the title rather than stating a verb and outcome. The only hint of function comes from the title ('Plan materials and spare stock'), not from the description itself, so an agent cannot tell from the description alone what the tool produces.

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?

It offers input conventions ('use the seller's model field or exact variant name', 'one consistent unit') but no when-to-use or when-not-to-use guidance relative to any alternative. The distinction between this planning tool and stock/review siblings is left entirely to inference.

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.