Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · KOKUYO Harinacs Handy Stapleless Stapler

tds_purchase_d25
Read-onlyIdempotent

Recorded model SLN-MSH110GB. 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_d25"
  }
}

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 that this is a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds some context about model identity and unit consistency, but it does not explain what the tool computes, what it returns, or how inputs are combined.

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 has no obvious filler, but it opens with a recorded model string rather than the tool’s action. The guidance is fragmented into naming, unit, and compatibility notes without a front-loaded statement of what the tool does.

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 five-parameter planning tool with no output schema, the description does not explain the calculation, expected output, or the roles of most inputs. It is not complete enough for an agent to confidently invoke this tool or interpret its results.

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. It partially clarifies that offeredModel should match the seller’s model or exact variant and that units should be consistent, but it leaves monthlyUse, months, unitsOnHand, unitsPerPack, and the planning formula largely undefined.

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 names a recorded model and gives naming/unit instructions, but it never states the operation being performed, such as calculating a purchase or usage plan. The title supplies some purpose, but the description itself does not clearly distinguish this tool from the many sibling purchase-planning tools.

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?

It gives input constraints like using the seller’s model field or exact variant name and keeping units consistent, but it does not say when to use this tool, when not to use it, or how to choose among alternatives. There is no actionable routing guidance beyond generic setup instructions.

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.