Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Pentel PLUS Deco Tape Pen-Style

tds_purchase_m_pentel_deco_tape
Read-onlyIdempotent

Recorded model PLUS Deco Tape Pen-Style. 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_m_pentel_deco_tape"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description discloses nothing about the computation itself: no statement of what is calculated, whether partial packs round up, whether unitsOnHand offsets need, or how the result is presented. Given no output schema, this silence leaves the core behavior opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short imperative sentences with no filler and no repetition, front-loaded with the model constraint. The trade-off is that its brevity is achieved by omission rather than by precision, but there is no wasted wording to penalize.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five required parameters at zero schema coverage and no output schema mean the description must explain the calculation and the units model; it does so only partially. An agent knows how to name the model but not what the tool returns or how to interpret months against unitsOnHand.

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%, so the description carries the full burden. It addresses offeredModel meaningfully (seller's model field or exact variant name) and gestures at unit consistency, which bears on monthlyUse versus unitsPerPack. But months, unitsOnHand and the pack-size semantics go entirely unexplained in both schema and 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 opens with "Recorded model PLUS Deco Tape Pen-Style," which restates the tool name rather than stating what the tool does. Nothing says this tool computes a usage or purchase plan (drawdown from unitsOnHand over months at monthlyUse, divided by unitsPerPack); only the title hints at planning. An agent cannot distinguish its operation from a lookup tool without inferring from the parameter names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It does give input-selection guidance: use the seller's model field or exact variant name, keep task and package units consistent, and confirm type/dimensions/compatibility. What it never says is when to reach for this tool versus the many sibling purchase tools, nor any prerequisite or exclusion. Usage is implied by the parameters, not stated.

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.