Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Tombow MONO Light Eraser

tds_purchase_m_tombow_mono_light_eraser
Read-onlyIdempotent

Recorded model MONO Light Eraser. 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_tombow_mono_light_eraser"
  }
}

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 safety is covered. The description adds nothing beyond that—it does not say what result is produced (planned units, pack rounding, spares) nor how sparePercent affects the outcome; the past-tense "Recorded" is ambiguous against a mutating-sounding "purchase" name.

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?

Only three short sentences with no filler, so there is little waste. However, the brevity comes at the cost of vague phrasing ("checked values for the exact pack or accessory") rather than front-loading a clear statement of what the tool does.

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 parameters, zero schema descriptions and no output schema, the description should carry the burden of explaining inputs and the planning result. It covers variant naming and unit consistency only, leaving the spare-stock percentage and per-project amounts undocumented for a quantity-planning tool.

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%, so all five required parameters depend on the description. It touches offeredModel (model field/variant name) and partly hints at unitsPerPack/amountPerProject via "one consistent unit," but leaves projects, sparePercent and amountPerProject unexplained, which is a substantial compensation gap.

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 MONO Light Eraser" identifies the resource but supplies no verb describing the operation; the reader must infer from the name/title that this plans purchase quantities and spare stock. It distinguishes the product variant but not the action performed on it.

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 hygiene advice (use the seller's model field or exact variant name, keep one consistent unit, use checked pack/accessory values) rather than when-to-use guidance. It never states which sibling tool to prefer for a different product or for quoting/spare-parts review, and offers no exclusions.

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.