Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Tombow MONO Drawing Pen

tds_purchase_m_tombow_mono_drawing_pen
Read-onlyIdempotent

Recorded model MONO Drawing Pen. 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_drawing_pen"
  }
}

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 establish readOnlyHint, idempotentHint, non-destructive, and closed-world behavior; the description adds no behavioral context such as whether it computes a plan, how spare stock is applied, or what is returned. It only gives input hygiene about model naming and units.

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 three short sentences it is not verbose, but the first sentence is redundant with the tool name/title and the remaining sentences jump into input hygiene without stating the core action. Structurally, the purpose should be front-loaded; here it is absent.

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?

For a five-required-parameter planning tool with no output schema, the description is far too thin: it does not explain the calculation, return values, or most parameter semantics. It only covers product identification and a unit-consistency caution, so an agent would still need to infer the core behavior.

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% for five required parameters, so the description must carry parameter meaning. It says something about offeredModel ("seller’s model field or exact variant name") and consistent units, but never explains projects, amountPerProject, unitsPerPack, or sparePercent, leaving most required inputs undefined.

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 first sentence, "Recorded model MONO Drawing Pen," merely restates the product/name and gives no verb or resource action. It never says the tool calculates purchase quantities, plans materials, or handles spare stock; the title says that, but the description itself does not.

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 instructs how to fill offeredModel and to use a consistent unit, but gives no when-to-use guidance, prerequisites, or alternatives to sibling product-specific tools. The only implied usage is the product model itself, which is not explicit routing guidance.

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.