Credit GPS — Canadian credit

Statement calendar

get_statement_calendar

Read-onlyIdempotent

Use this when someone asks about timing, what is coming up, or why the closing date differs from the due date. Returns the upcoming dates in order: when to pay, when each statement closes (the bureau read), and when each payment is due (the delinquency line). Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input Schema

Name	Required	Description
`cards`	Yes	The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
`count`	No	How many events to return. Default 8.
`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.

Output Schema

Name	Required	Description	Default
`events`	Yes
`disclosure`	Yes
`assumptions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the description only needs to add context — and it does: it calculates from supplied figures, fetches nothing external, and explicitly retains no tool inputs. That privacy/no-retention note is genuine value beyond the annotations.

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?

The usage trigger is front-loaded in the first clause, followed by the return shape ordered as it will be returned, then a compact exclusion list. No sentence is filler and nothing is buried.

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?

With an output schema present, the description need not explain return values, and it still summarizes the ordering of events. Combined with exhaustive parameter docs, an agent has enough to call it correctly; only the count/today defaults are left entirely to the schema.

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 coverage is 100%, so cards/count/today are all fully documented in the schema, and the baseline is 3. The description adds only the vague phrase 'calculates scenarios from supplied figures' without clarifying count, today, or the date-driven inputs beyond what the schema says.

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 and resource: returns upcoming statement dates in order (pay date, close date, due date), and frames it around the closing-vs-due distinction. It does not explicitly name which sibling to prefer (e.g. find_statement_close_date), but the calendar-ordering purpose is unmistakable.

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 trigger conditions: 'when someone asks about timing, what is coming up, or why the closing date differs from the due date.' It also lists what the tool does not do (no payments, no account changes, no external fetch), which steers the agent away from misuse, though it never names an alternative sibling 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?