Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Altenew Mountain Die Set

tds_purchase_m_altenew_mountain_die_set
Read-onlyIdempotent

Recorded model Mountain Die 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_mountain_die_set"
  }
}

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, idempotentHint and non-destructive, so safety is covered. The description adds only a data-consistency rule (one consistent unit, checked pack/accessory values) and says nothing about what is computed or returned, leaving the actual behavior of this planning tool opaque.

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, so it is efficiently sized. However, the first sentence is near-zero information and is placed where the action statement should be, so brevity comes at the cost of front-loading the wrong content.

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-parameter, fully-required computation tool with no schema descriptions and no output schema needs the description to explain the calculation and the meaning of projects and sparePercent. It does neither, so an agent would have to guess how the inputs combine.

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 coverage is 0% across five required parameters, so the description carries the full burden. It glosses offeredModel and hints at unitsPerPack/amountPerProject through the unit-consistency rule, but never explains projects, sparePercent, or how the numeric bounds should be interpreted.

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?

"Recorded model Mountain Die Set" restates the product identity but never states what the tool does with it. The title's action ("plan materials and spare stock") never appears in the description, so an agent cannot tell whether this records a purchase, computes pack requirements, or opens a plan.

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 offers input conventions ("use the seller's model field or exact variant name") but no when-to-use guidance and no routing to alternatives. Neighbors like tds_spare_parts_review or tds_threshold_spare_stands are not referenced, so the agent gets no signal about which tool applies when.

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.