Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Altenew Tree Ring Stencil

tds_purchase_m_altenew_tree_ring_stencil
Read-onlyIdempotent

Recorded model Tree Ring Stencil. 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_tree_ring_stencil"
  }
}

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 safety is covered. The description adds only a unit-consistency instruction and says nothing about what the tool returns or how spare stock is calculated, which is the behavior an agent most needs here; no contradiction with the annotations.

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 are not bloated, but the lead sentence is filler that repeats the product name rather than front-loading the action. The substantive guidance (model field, unit consistency) appears after the wasted opening.

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-required-parameter planning computation with no output schema and no schema descriptions, so the description should explain the calculation inputs (projects, amount per project, spare percent, units per pack). It covers at most one of these, leaving an agent unable to reason about what the inputs mean or what result to expect.

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 partially explains offeredModel (seller's model field or exact variant name) and touches units, but projects, amountPerProject and sparePercent are entirely unexplained, and the "checked values for the exact pack or accessory" phrasing maps to no identifiable parameter.

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 Tree Ring Stencil" merely restates the product name already encoded in the tool name and title; it never says what the tool actually does (compute pack counts, spare units, material totals). The only hint at an action comes from the title "Plan materials and spare stock," not from the description body, so an agent must infer the verb and outcome.

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 input conventions ("use the seller's model field or exact variant name") but no when-to-use context, no prerequisites, and no differentiation from the many sibling purchase/stock tools. Nothing tells an agent when this product-specific planner applies versus a generic stock tool like tds_spare_parts_review.

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.