Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Archive sleeve purchase

tds_budget_sleeves_and_labels
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Archive sleeve purchase. Reserve for labeling (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>",
      "labelReserveCents": "<labelReserveCents>"
    },
    "name": "tds_budget_sleeves_and_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
labelReserveCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the computation order (reserve, subtract commitments, floor to whole units), which is genuinely useful behavior, but it never states what is returned — critical since no output schema exists — and the 'Archive sleeve purchase' line conflicts tonally with a pure read calculation.

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

Conciseness2/5

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

Three short fragments rather than coherent prose, and the middle fragment 'Archive sleeve purchase' is a dangling label that adds no information about behavior. The 'Reserve for labeling (cents)' tail is tacked on rather than integrated into the calculation description.

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?

Four required numeric parameters with zero schema descriptions and no output schema mean the description carries most of the burden, and it does not deliver: the return value is only vaguely implied and the archive/label ambiguity is unresolved. For a calculator whose entire contract is its inputs and result shape, this is under-specified.

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 all four integer parameters are undocumented structurally; the description partially compensates by naming the concepts (budget, commitments, per-unit cost, label reserve) and noting 'cents' as the unit. However, it does not tie these names to the exact parameter keys, explain that costPerUnitCents must be at least 1, or clarify how the division/flooring uses each 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 first sentence does describe an arithmetic operation — reserve a cost, subtract commitments, yield whole affordable units — which is more specific than the title. But the second sentence, "Archive sleeve purchase," is a disconnected title fragment that muddles whether this is an archive action or a budget calculation, and there is no differentiation from the many tds_budget_* and tds_*_reserve siblings.

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?

No when-to-use guidance is given at all: nothing says whether this is a pre-purchase affordability check versus a reservation record, and no alternative is named despite obvious candidates like tds_labels_reserve, tds_sleeve_reserve, or the other tds_budget_* calculators. The agent must infer usage from the name alone.

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.