Credit GPS — Canadian credit

About Credit GPS

describe_credit_gps

Read-onlyIdempotent

Use this when someone asks what Credit GPS is, who made this, whether their data is stored, or why an answer stopped short. Also explains how to obtain free Canadian bureau reports and manually enter their figures in the Credit GPS application for score tracking. This tool provides instructions; it cannot save entries or retrieve score history. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`what`	Yes
`limits`	Yes
`privacy`	Yes
`product`	Yes
`sources`	Yes
`disclosure`	Yes
`manualReportGuide`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 7, 2026

addedOutput schema / properties / manualReportGuide

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / sources

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "what",
-  "privacy",
-  "limits",
-  "product",
-  "disclosure"
-]New value: +[
+  "what",
+  "privacy",
+  "limits",
+  "product",
+  "manualReportGuide",
+  "sources",
+  "disclosure"
+]

AddedSep 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavioral limits: it cannot save entries, retrieve score history, fetch live data, or change accounts. This gives agents a precise model of what the tool can and cannot do.

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?

The description is front-loaded with usage guidance and keeps each sentence informative. It is slightly dense, but given the 0-parameter schema and the need to explain both the tool's purpose and limitations, the length is justified.

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?

For a no-parameter informational tool with an output schema, the description covers the key scenarios, the data privacy question, the manual entry workflow, and the tool's limitations. Nothing essential 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?

The tool has zero parameters, so the baseline is 4. The description adds that it returns bundled reference material 'optionally filtered or calculated from inputs,' which is useful context even though no schema parameters exist.

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 names a specific resource ('Credit GPS' itself) and enumerates concrete use cases: explaining what it is, who made it, data storage, shortened answers, and bureau report entry. This clearly differentiates it from sibling tools that explain credit mechanics or simulate paydowns.

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 description explicitly begins with 'Use this when someone asks...' and lists the exact triggers. It does not name sibling tools or state when not to use it, but the context is clear enough for an agent to route appropriately.

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?