Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Buying archival binders

tds_budget_binder_covers
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Buying archival binders. Reserve for matching inserts (cents).

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": {
      "budgetCents": "<budgetCents>",
      "committedCents": "<committedCents>",
      "costPerUnitCents": "<costPerUnitCents>",
      "insertReserveCents": "<insertReserveCents>"
    },
    "name": "tds_budget_binder_covers"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
insertReserveCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare a pure, safe, idempotent read calculation, so the description carries a lighter burden. It adds a useful behavioral detail — that an insert reserve is held back before units are computed — but does not state whether the result is an integer count, leftover budget, or both.

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?

It is short and front-loads the computation, which is good, but it reads as fragmented fragments rather than a coherent sentence, and the domain tag 'Buying archival binders' adds little operative meaning.

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?

For a four-parameter calculation with no output schema, the description should at minimum specify the return value (unit count, remaining budget, or both) and the rounding behavior. It gives a partial formula sketch but leaves the output contract unstated.

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 must compensate and only partly does: it clarifies that 'insertReserve' relates to matching inserts and that all values are in cents, and 'commitments' maps to committedCents. budgetCents and costPerUnitCents are never named or explained, and 'the named cost' does not map cleanly to any single field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description outlines a computation sequence (reserve cost, subtract commitments, compute whole affordable units), which hints at a budget-to-unit-count calculator. However, 'the named cost' is ambiguous and it never plainly says what the tool returns, so the purpose is only loosely inferable.

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 when-to-use guidance, no prerequisites, and no reference to any alternative. With 30+ siblings including many other tds_budget_* tools, the agent is left to guess whether this is the right budgeting tool.

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.