Skip to main content
Glama

Loan Balloon Balance

bpj_loan_balloon_balance
Read-onlyIdempotent

Project the outstanding balloon after fixed month-end payments with nominal interest compounded monthly.

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": {
      "principal": "<principal>",
      "nominal": "<nominal>",
      "months": "<months>",
      "payment": "<payment>"
    },
    "name": "bpj_loan_balloon_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
nominalYes
paymentYes
principalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered externally. The description usefully adds the calculation convention (nominal rate compounded monthly, payments at month-end), which materially changes results, but says nothing about output shape or what happens when payments fail to cover interest (negative or undefined balloon).

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

Conciseness4/5

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

A single front-loaded sentence with no filler or repetition. Dense and readable, though it leaves no room for the additional constraints the tool actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pure deterministic four-parameter calculator whose annotations already establish it as a safe, closed, idempotent read, the description covers the model needed to call it correctly; no output schema exists, so return-value explanation is not strictly required. Gaps are modest: term behavior at zero/insufficient payment and the exact returned quantity remain unspecified.

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 has to carry meaning, and it does clarify that 'nominal' is an annually-quoted rate compounded monthly and that 'payment' occurs at end of month. It does not clarify that payments recur for exactly the 'months' periods, nor the unit conventions or acceptable ranges beyond what the parameter titles already state.

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

Purpose4/5

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

States a specific verb ('Project') and a specific computed resource ('outstanding balloon') along with the model assumptions (fixed month-end payments, nominal interest compounded monthly). An agent can distinguish this from the sibling bpj_fixed_loan_payment, which solves the inverse problem, though the description never names that alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description makes clear this computes a remaining balance given a fixed payment stream, but it never says when to prefer it over the sibling payment-solver, nor does it state prerequisites such as payments being constant for the whole term or whether periods are whole months only.

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.