Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Tombow TwinTone Marker

tds_purchase_m_tombow_twintone_marker
Read-onlyIdempotent

Recorded model TwinTone Marker. 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_twintone_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/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 without description help. The description adds a little operational context (use one consistent unit, supply checked pack/accessory values), implying validation concerns, but says nothing about what the tool computes or returns, or what happens on inconsistent 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?

Three short sentences with no bloat, but the leading sentence is wasted space that duplicates the title's product name instead of stating the operation. The useful content (model field, unit consistency, checked pack values) comes after the throwaway opener rather than being front-loaded.

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, no output schema and no annotation coverage of inputs, the description would need to explain the planning model (per-project amounts, pack conversion, spare percentage). It covers none of that math or the response shape, so an agent cannot confidently supply inputs or interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 load and it only partially does: it explains offeredModel (seller's model field or exact variant name) and gestures at the pack/unit parameters. projects, amountPerProject and sparePercent are never explained, leaving three of five required inputs without meaning beyond their names and numeric bounds.

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 description opens with "Recorded model TwinTone Marker," which restates the product name in the title rather than naming an action the tool performs. It never states that the tool computes material quantities and spare stock (the only hint is the title), so an agent cannot tell what invoking it actually does.

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?

There is no when-to-use guidance, no mention of when to pick a different purchase/planning sibling, and no prerequisites or preconditions. The sentences that exist are data-entry rules for parameters, not 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.