Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Tombow MONO Zero Rectangular Eraser

tds_purchase_d23
Read-onlyIdempotent

Recorded model 57306. 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_d23"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds nothing beyond that — it does not say whether the tool computes a suggested order quantity, what happens if unitsOnHand exceeds need, or what the caller gets back, despite having no output schema.

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 little waste, so it is not bloated. However, the front-loaded sentence is a model number rather than the tool's function, so the structure prioritizes identification over the information an agent most needs.

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, all-required tool with zero schema descriptions and no output schema demands a description that explains the calculation and the units contract. This one covers only model matching, leaving an agent unable to know how monthlyUse, months and unitsOnHand combine or what result to expect.

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% across five required parameters, so the description must carry the burden and largely does not. 'Use the seller's model field or exact variant name' helps map to offeredModel, and the 'same measured unit' note hints that monthlyUse and unitsPerPack must be commensurate, but months, unitsOnHand and unitsPerPack are never explained.

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 does — no verb, no output, no mention of planning or computing a purchase quantity. It opens with 'Recorded model 57306' and spends its sentences on product identification, leaving the purpose to be inferred from the title 'Plan paper or media use' rather than from the description text.

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 guidance given ('use the seller's model field or exact variant name', 'confirm the exact type, dimensions and compatibility') is about matching the product, not about when to call this tool versus the many sibling tds_purchase_m_* tools. There is no statement of preconditions, alternatives, or when this planning tool is the right choice.

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.