Skip to main content
Glama

Credit GPS — Canadian credit

What closing a card does to utilization

estimate_close_card_impact
Read-onlyIdempotent

Use this for "should I cancel the credit card I never use", "is it bad to close a card", or any question about cancelling, downgrading, or consolidating cards. It does not close, cancel, or change any card; it only explains and calculates. With no card figures it returns general closure considerations and retention information. Supply figures for a hypothetical paid-off closure calculation. Supply cards and cardName as well and it additionally computes the exact utilization before and after, the limit leaving the denominator, and whether it crosses a band upward. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estimate_close_card_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsNoThe person's cards, if they have given them. Omit to get the mechanics and the Canadian rules without any numbers.
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.
cardNameNoThe card being considered for closure. Partial names are matched. Only meaningful alongside cards.

Output Schema

NameRequiredDescriptionDefault
cardNameYes
computedYes
bandAfterYes
alwaysTrueYes
bandBeforeYes
disclosureYes
assumptionsYes
blendedAfterYes
limitRemovedYes
balanceOnCardYes
blendedBeforeYes
crossesBandUpYes
remainingLimitYes
isOnlyRevolvingAccountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • removedOutput schema / properties / balanceOnCard / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / balanceOnCard / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / blendedAfter / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / blendedAfter / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / blendedBefore / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / blendedBefore / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / cardName / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / cardName / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / crossesBandUp / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / crossesBandUp / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / isOnlyRevolvingAccount / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / isOnlyRevolvingAccount / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / limitRemoved / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / limitRemoved / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / remainingLimit / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / remainingLimit / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, but the description adds substantial non-structured context: graceful degradation to general closure/retention info when no card figures are supplied, a hypothetical paid-off closure model, and explicit statements that it makes no payments, changes no accounts, fetches no external data, and retains no inputs.

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-loads the trigger phrases an agent matches on, then layers the mode behavior. Dense but every sentence carries information; the closing 'does not make payments, change accounts, fetch external data, or retain tool inputs' slightly repeats the earlier non-mutation disclaimer.

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?

Output schema exists, so return shapes needn't be spelled out, and the description still explains what each input mode produces and what happens when optional data is omitted. For a read-only estimator with three optional parameters, nothing an agent needs to 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 conditional semantics the schema can't express: cards alone yields a closure calculation, while cards plus cardName additionally yields before/after utilization, the limit leaving the denominator, and band-crossing detection. It also notes cardName is only meaningful alongside cards, which clarifies a real dependency.

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?

States a specific verb and resource — calculating/explaining the utilization impact of closing a card — and immediately bounds it: 'It does not close, cancel, or change any card; it only explains and calculates.' That separates it cleanly from mutating or payoff-simulation siblings like simulate_paydown and calculate_payoff_timeline.

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

Usage Guidelines4/5

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

Gives concrete user-question triggers ('should I cancel the credit card I never use', 'is it bad to close a card') and a scope of cancelling, downgrading, and consolidating. It also sets the no-data vs with-data usage modes. It stops short of naming a sibling alternative for overlapping questions (e.g. compare_cards_for_purchase or simulate_paydown), so it's clear context without explicit routing.

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