Skip to main content
Glama

Credit GPS — Canadian credit

How long to pay this card off

calculate_payoff_timeline
Read-onlyIdempotent

Use this for "if I pay $200 a month, when is this paid off?" or "what happens if I only pay the minimum?". Returns how long a card takes to clear at a fixed monthly payment and the interest paid over that time. This is a cost question, not a reporting one: it does not change what the bureaus see, so use get_reported_snapshot or simulate_paydown for that. Requires the card's purchase APR; without it no timeline is returned, because the rate decides the answer. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

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": {
      "cards": "<cards>",
      "cardName": "<cardName>"
    },
    "name": "calculate_payoff_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYesThe person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
todayNoToday's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.
cardNameYesWhich card to pay off. Partial names are matched.
monthlyPaymentNoFixed amount paid each month in CAD. Omit to use the card's minimum payment, if one was supplied.

Output Schema

NameRequiredDescriptionDefault
aprBpsYes
monthsYes
balanceYes
cardNameYes
atMinimumYes
aprUnknownYes
disclosureYes
assumptionsYes
neverShrinksYes
totalInterestYes
monthlyPaymentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / aprBps / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / aprBps / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / atMinimum / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "monthlyPayment": {
      -        "type": "number"
      -      },
      -      "months": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "neverShrinks": {
      -        "type": "boolean"
      -      },
      -      "totalInterest": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "required": [
      -      "monthlyPayment",
      -      "months",
      -      "totalInterest",
      -      "neverShrinks"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "monthlyPayment": {
      +        "type": "number"
      +      },
      +      "months": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "neverShrinks": {
      +        "type": "boolean"
      +      },
      +      "totalInterest": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "monthlyPayment",
      +      "months",
      +      "totalInterest",
      +      "neverShrinks"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / months / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / months / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / totalInterest / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / totalInterest / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description agrees with them while adding a real precondition: without the card's purchase APR no timeline is returned, because the rate determines the answer. The negative capability list (no payments, no account changes, no external fetch, no input retention) reinforces rather than contradicts the annotations, though parts of it restate what the hints already say.

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?

Front-loaded with the user-question framing and the return values, with routing guidance before the negative list. Slightly padded by the four-item 'does not...' clause that partly duplicates the annotations.

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, annotations cover the safety profile, and schema documentation is complete, so the description only needed to add trigger, routing, precondition, and scope — all present. Nothing an agent needs to select or invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: monthlyPayment is contextualized as the fixed monthly figure driving the calculation, and aprPercent is escalated from 'omit when unknown' into a hard requirement for a meaningful result. It still does not clarify the cardName-vs-cards relationship or how minimum payment fallback interacts with monthlyPayment.

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?

Names a specific computation (months to clear a balance at a fixed monthly payment) and its second output (interest paid over that time), framing it with the exact user questions it answers. It explicitly distinguishes itself from get_reported_snapshot and simulate_paydown, so an agent can route without opening either 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?

Opens with concrete trigger phrasings ('if I pay $200 a month, when is this paid off?', 'what happens if I only pay the minimum?') and states the exclusion plus the named alternatives for the excluded case. The 'cost question, not a reporting one' framing gives a clean decision rule.

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.

Resources