Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Altenew Milky Way Stencil

tds_purchase_m_altenew_milky_way_stencil
Read-onlyIdempotent

Recorded model Milky Way 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_milky_way_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 closed-world scope, so the safety profile is covered. The description adds only unit-consistency advice and does not explain what the tool computes (e.g., how projects, amountPerProject and sparePercent combine into a total). It does not contradict the annotations, but it adds little behavioral context on top of them.

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?

At two short sentences it is not bloated, but the first sentence is wasted on a name restatement. The actionable guidance (model field, consistent units, checked pack values) is present but not ordered by importance relative to the required inputs.

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?

With five required, wholly undocumented parameters and no output schema, the description should explain the quantity model. It instead covers only naming and unit conventions, leaving an agent unable to tell what sparePercent or amountPerProject mean in practice. Annotations cover safety, but the computational semantics are missing.

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 meaning. It only loosely gestures at offeredModel ("seller's model field or exact variant name") and unitsPerPack ("one consistent unit"), and leaves projects, amountPerProject, and sparePercent entirely unexplained. The relationship between per-project amounts and spare percentage is the crux of the tool and goes unmentioned.

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 Milky Way Stencil" effectively restates the tool name and title without stating a verb or the operation performed. The actual purpose (planning material amounts and spare stock across projects) only appears in the title, not in the description an agent reads. Nothing distinguishes it from the many sibling product-specific purchase/stock tools.

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 two sentences give input hygiene advice (use the seller's model field, keep units consistent, check pack/accessory values), not when-to-use guidance. There is no mention of when this product-planning tool should be chosen over stock tools like tds_billing_show_stock, tds_spare_parts_review, or tds_quote_framing_plan. An agent gets no routing signal beyond the product name.

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.