Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Sakura Pigma Micron Fineliner

tds_purchase_d22
Read-onlyIdempotent

Recorded model Pigma Micron. Use the seller’s model field or exact variant name. Use the same measured unit for your task and the package. Confirm the exact type, dimensions and compatibility.

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>",
      "monthlyUse": "<monthlyUse>",
      "months": "<months>",
      "unitsOnHand": "<unitsOnHand>",
      "unitsPerPack": "<unitsPerPack>"
    },
    "name": "tds_purchase_d22"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by warning to use a consistent measured unit and to confirm compatibility, but it does not explain what the tool returns or how it performs its planning calculation.

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?

The description is short and avoids bloat, but the first sentence is an unhelpful fragment that does not front-load the tool's purpose. The remaining sentences are instructions without a clear frame, so the structure is functional but weak.

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 tool with five required parameters, no output schema, and no schema descriptions, the definition is incomplete. It does not state the calculation or result, and it omits meaningful definitions for most inputs. This is insufficient for an agent to invoke the tool confidently.

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 the description must compensate. It only clarifies 'offeredModel' and vaguely gestures at unit consistency; it leaves 'monthlyUse', 'months', 'unitsOnHand', and 'unitsPerPack' unexplained. An agent cannot reliably interpret most of the required inputs from this description.

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 never states what the tool actually does. It opens with the fragment 'Recorded model Pigma Micron' and gives usage instructions, but there is no verb or operation such as calculating required packs. An agent cannot tell from the description alone whether this records, looks up, or plans a purchase.

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 guidance on when to use this tool versus the many sibling purchase-planning tools. The instructions about model fields, units, and compatibility are parameter-level advice, not selection criteria. The agent must infer the tool's role from the title.

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.