Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Talens Pigment Fineliner

tds_purchase_m_talens_talens_pigment_fineliner
Read-onlyIdempotent

Recorded model Pigment Fineliner. 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_talens_talens_pigment_fineliner"
  }
}

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds a useful vetting cue ('confirm the exact type, dimensions and compatibility') but says nothing about how the calculation behaves, rounding, or what the result represents.

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 filler, but the lead sentence is a tautology that consumes the most prominent position. The actionable constraints are present yet underspecified in wording.

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?

A five-parameter, fully required computation tool with no parameter descriptions and no output schema needs the description to explain the units semantics and expected result. The description leaves the core computation and the unitsOnHand vs unitsPerPack distinction unexplained.

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% for five required params, so the description must compensate and largely does not. It only gestures at 'offeredModel' and 'the same measured unit' (vaguely monthlyUse/unitsOnHand/unitsPerPack); it never distinguishes unitsOnHand from unitsPerPack nor explains 'months'.

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 Pigment Fineliner' restates the product identity from the tool name and never states the action: nothing says it computes a purchase plan, pack count, or shortfall from monthly use over N months. An agent must infer the operation entirely from the title and 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 Guidelines2/5

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

The description gives data-entry advice ('use the seller's model field or exact variant name', 'same measured unit') but no when-to-use, when-not-to-use, or comparison against sibling product-planning tools. No exclusions or preconditions are 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.