Skip to main content
Glama
Credit Karma MCP

Credit Karma MCP

by chrischall

ck_list_transactions

Read-only

List and filter stored Credit Karma transactions newest first, with pagination and optional merchant, account, category, status, date, and amount filters.

Instructions

List transactions with optional filters, newest first. Paginated. Reads the local database (filled by ck_sync_transactions). view "brief" answers one line per transaction instead of JSON.

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_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"full" (default) returns the JSON page; "brief" returns one line per transaction: merchant and signed amount — date (YYYY-MM-DD, or "no date") — status, inside the untrusted-data envelope, with "-- " note lines for an empty ("-- none") or partial ("-- N of M shown") page.
limitNoDefault 50; a whole number from 1 to 500
offsetNoDefault 0; a whole number, 0 or more
statusNoe.g. posted, pending, cancelled
accountNoPartial account name match
categoryNoPartial category name match
end_dateNoYYYY-MM-DD
merchantNoPartial merchant name match
max_amountNoMaximum absolute amount
min_amountNoMinimum absolute amount
start_dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.0
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns the JSON page; \"brief\" returns one line per transaction: merchant and signed amount — date (YYYY-MM-DD, or \"no date\") — status, inside the untrusted-data envelope, with \"-- \" note lines for an empty (\"-- none\") or partial (\"-- N of M shown\") page.",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. Changed8 schema fields changedv3.3.3
    • changedInput schema / properties / limit / description
      Previous value: -"Default 50"New value: +"Default 50; a whole number from 1 to 500"
    • addedInput schema / properties / limit / maximum
      Added value: +500
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / offset / description
      Previous value: -"Default 0"New value: +"Default 0; a whole number, 0 or more"
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  3. Changed1 schema field changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observedv2.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: results are newest-first, the response is paginated, data comes from a local DB populated by ck_sync_transactions, and the 'brief' view yields one line per transaction rather than JSON.

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?

Three short sentences, front-loaded with the core action, then pagination/ordering, then the data source and view mode. No filler or redundancy.

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?

For an 11-parameter read tool with no output schema, the description covers ordering, pagination, data provenance, and the alternate view format. It omits edge-case behavior (e.g., empty results) but the schema and annotations fill most remaining gaps.

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%, so every parameter is already documented, including the view enum and its output format. The description's note about 'brief' restates what the schema already explains, adding little new meaning; baseline 3 applies.

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 ('List transactions') plus scope details: optional filters, newest-first ordering, pagination. It does not differentiate from the close sibling ck_get_recent_transactions, which an agent could easily confuse with this tool.

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

Usage Guidelines3/5

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

The mention that it reads the local database 'filled by ck_sync_transactions' implies a prerequisite (sync first), which is useful. However, there is no explicit guidance on when to choose this over ck_get_recent_transactions or ck_query_sql, so the agent must infer the boundary.

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