Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Display loan handoff

tds_budget_handing_loan
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Display loan handoff. Return freight reserve (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>",
      "returnFreightReserveCents": "<returnFreightReserveCents>"
    },
    "name": "tds_budget_handing_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
returnFreightReserveCentsYes

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 safety is covered and the bar is lower. The description adds real value by disclosing the arithmetic sequence and that the freight reserve result is expressed in cents, but 'Reserve the named cost' carries a mutation flavor that is not fully disambiguated as pure calculation, and nothing is said about rounding/overflow behavior for the large integer bounds.

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 the arithmetic step is front-loaded, which is good. However, the second sentence 'Display loan handoff' earns no place — it repeats the title, adds no actionable information, and actively distracts from 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?

For a four-parameter, all-required tool with no output schema and no param descriptions, the definition leaves too much unspecified: which input is the budget, what 'whole affordable units' means numerically, and how the freight reserve relates to the unit count. A caller would have to guess the semantics of half the inputs.

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 four required parameters, so the description must compensate and only partly does: 'commitments' plausibly maps to committedCents and 'return freight reserve (cents)' maps to returnFreightReserveCents, but budgetCents is never mentioned and 'the named cost' does not clearly identify costPerUnitCents. Units and bounds for the inputs remain undocumented.

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 does convey a computation flow (subtract commitments, calculate whole affordable units) tied to the budget/loan name, but it never states plainly what the tool returns as a whole or what 'Reserve the named cost' means. The sentence 'Display loan handoff' is a title fragment with no discernible meaning here, muddling rather than clarifying purpose.

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 guidance on when to pick this tool over the many budget_*, handoff_*, and billing_* siblings, nor any statement of prerequisites or exclusions. The only implicit context is that it deals with budget arithmetic, which an agent could guess 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.