Credit GPS — Canadian credit

Multi-step credit plan

get_credit_plan

Read-onlyIdempotent

Use this when someone wants more than the next single action. Returns an ordered plan for one of three goals: raise_score, pay_down_balances, or build_credit. Safety steps come first (anything overdue, then imminent minimums), then goal steps, each with the specific action, the mechanism behind it, and a date. The plan is returned as text and structured data for the person to act on themselves; nothing is scheduled or executed. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input Schema

Name	Required	Description
`goal`	Yes	Which goal to plan for.
`cards`	Yes	The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
`today`	No	Today'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.
`targetUtilization`	No	Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band.

Output Schema

Name	Required	Description	Default
`goal`	Yes
`steps`	Yes
`disclosure`	Yes
`assumptions`	Yes
`generatedForDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 25, 2026
- removedOutput schema / properties / steps / items / properties / accountName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / steps / items / properties / accountName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / steps / items / properties / amount / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / steps / items / properties / amount / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / steps / items / properties / dueByDate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / steps / items / properties / dueByDate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedSep 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only, non-destructive, idempotent, closed-world behavior. The description adds substantial context: the plan is text plus structured data, nothing is scheduled or executed, no payments or account changes occur, no external data is fetched, and inputs are not retained.

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

Conciseness5/5

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

Five sentences, front-loaded with the usage trigger and purpose, then output ordering, return format, and side-effect boundaries. Every sentence contributes useful information, with no filler.

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?

Complete for a read-only planning tool: it states input dependency, output form, step ordering, and absence of side effects, and an output schema exists. It could better route against planning-adjacent siblings like simulate_paydown and calculate_payoff_timeline.

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%, with detailed per-field descriptions for goal, cards, today, and targetUtilization. The description adds little parameter-specific meaning beyond mentioning the three goals and that scenarios are calculated from supplied figures, so baseline 3 applies.

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: 'Returns an ordered plan' for 'credit plan' goals. It enumerates the three goals and distinguishes itself from single-action siblings with 'more than the next single action.'

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?

The opening sentence gives a clear trigger: use when someone wants more than the next single action. It does not explicitly name alternatives such as get_next_move or simulate_paydown, nor does it state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Credit GPS — Canadian credit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?