Skip to main content
Glama
Sign In
Credit Karma MCP

Credit Karma MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ck_forget_session

DestructiveIdempotent

Delete the saved Credit Karma session and clear in-memory credentials to remove stored login. Works locally without contacting Credit Karma.

Instructions

Forget the Credit Karma session on this machine: delete the saved-session file (~/.creditkarma-mcp/session, or CK_SESSION_PATH) that ck_set_session and token refreshes write, and clear the credentials held in memory. Use when the user stops using this server or wants their stored login removed. Local only — Credit Karma is not contacted, synced transactions are kept, and a CK_COOKIES value set in the host config is not changed.

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": "ck_forget_session"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.3

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already signal destructive and idempotent behavior, and the description adds substantial context beyond them: the exact file path (~/.creditkarma-mcp/session or CK_SESSION_PATH), in-memory credential clearing, no network contact, and preservation of synced transactions and host config values. This fully discloses side effects.

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 description is information-dense without redundancy: the primary action and file path come first, followed by the usage condition, then important exclusions. Every sentence adds operational value, and the caveats are separated clearly.

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 state-clearing destructive tool with no output schema, the description covers all an agent needs: exact target file, environment variable override, in-memory effect, local-only guarantee, and what is intentionally preserved. Nothing necessary for correct invocation or safe reasoning 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 and the schema coverage is 100%, so the schema carries no semantic burden. With no parameters to describe, the baseline of 4 applies; the description appropriately focuses on behavior instead of parameters.

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 uses a specific verb ('Forget') and a clear resource ('Credit Karma session on this machine'), then spells out the concrete mechanism: deleting the saved-session file and clearing in-memory credentials. It also distinguishes the tool from its sibling ck_set_session by explicitly naming the session file both tools write to.

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?

The description states exactly when to use the tool: 'when the user stops using this server or wants their stored login removed.' It also clarifies boundaries by listing what is not affected (synced transactions, CK_COOKIES) and that it is local-only, preventing misuse as a remote logout.

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

Deploy Server

Other Tools