Skip to main content
Glama

EveryCalc

calculate_credit_card_payoff

Read-onlyIdempotent

Months and interest to clear a credit card balance with a fixed monthly payment, compared with adding an extra monthly payment. A payment that never clears the balance returns null months and interest. Use when the user wants to clear a credit card balance and asks how long it takes or how much interest it costs. For several different debts use calculate_debt_payoff. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive credit card payoff calculator.

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": {
      "balance": "<balance>",
      "annual_rate_pct": "<annual_rate_pct>",
      "monthly_payment": "<monthly_payment>"
    },
    "name": "calculate_credit_card_payoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
balanceYesCard balance in USD.
extra_paymentNoExtra payment added each month in USD; default 0.
annual_rate_pctYesCard APR percent.
monthly_paymentYesBase monthly payment in USD.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the calculation succeeded.
noteYesDisclaimer that accompanies every result.
toolYesName of the tool that ran.
inputsNoThe normalized inputs the calculation used.
resultsYesThe computed figures for this calculator.
calculator_urlYesDeep link to the matching interactive calculator on everycalc.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "Disclaimer that accompanies every result.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "ok",
      -  "tool",
      -  "results",
      -  "calculator_url"
      -]New value: +[
      +  "ok",
      +  "tool",
      +  "results",
      +  "calculator_url",
      +  "note"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "calculator_url": {
      +      "description": "Deep link to the matching interactive calculator on everycalc.xyz.",
      +      "type": "string"
      +    },
      +    "inputs": {
      +      "description": "The normalized inputs the calculation used.",
      +      "type": "object"
      +    },
      +    "ok": {
      +      "description": "True when the calculation succeeded.",
      +      "type": "boolean"
      +    },
      +    "results": {
      +      "description": "The computed figures for this calculator.",
      +      "type": "object"
      +    },
      +    "tool": {
      +      "description": "Name of the tool that ran.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "ok",
      +    "tool",
      +    "results",
      +    "calculator_url"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the safety burden is lifted. The description adds real behavioral context beyond that: the degenerate case where a payment never clears the balance returns null months and interest, plus a required post-call action (surface calculator_url as a clickable markdown link). It does not describe rounding/currency assumptions, but the disclosed edge case is substantive.

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?

Three sentences, purpose and comparison front-loaded, then usage routing, then the link instruction. The IMPORTANT clause is operational rather than semantic but it is short and directly actionable. No filler sentences.

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

Completeness5/5

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

An output schema exists, so return-field documentation is not owed by the description; the description nonetheless flags the one non-obvious return behavior (null months/interest on a never-clearing payment) and the one output the agent must act on (calculator_url). Combined with 100% schema coverage, an agent has everything needed to call and use this correctly.

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 100%, so all four parameters (balance, annual_rate_pct, monthly_payment, extra_payment) are already documented with units in the schema. The description adds only indirect framing — that monthly_payment is the base and extra_payment the optional add-on — without new syntax, defaults, or constraints. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose5/5

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

The description states a specific verb+resource ('months and interest to clear a credit card balance') and the precise comparison it performs: fixed monthly payment vs. an added extra payment. It explicitly names the sibling it is not ('For several different debts use calculate_debt_payoff'), so an agent can disambiguate from the many other calculate_* tools without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('Use when the user wants to clear a credit card balance and asks how long it takes or how much interest it costs') and an explicit alternative with its own condition (multiple debts → calculate_debt_payoff). Both the when and the when-not are stated.

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.