Skip to main content
Glama
chrischall

Credit Karma MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ck_query_sql

Read-only

Execute read-only SQL SELECT queries (including CTEs) on transaction, account, category, and merchant data. Returns up to 5,000 rows; page larger results with LIMIT/OFFSET.

Instructions

Execute a raw SQL SELECT query (CTEs via WITH ... SELECT are supported) against the transactions database. Non-SELECT statements (INSERT, UPDATE, DELETE, DROP, etc.) are rejected. Returns at most max_rows rows (default 500, max 5000); a larger result comes back with truncated: true, so prefer aggregates or LIMIT/OFFSET paging. Tables: transactions, accounts, categories, merchants, sync_state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYesA SELECT SQL statement
max_rowsNoMost rows to return (default 500). Page larger results with LIMIT/OFFSET.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.3
    • addedInput schema / properties / max_rows
      Added value: +{
+  "description": "Most rows to return (default 500). Page larger results with LIMIT/OFFSET.",
+  "maximum": 5000,
+  "minimum": 1,
+  "type": "integer"
+}
  2. 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"
  3. First observedv2.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description substantially enriches this by disclosing that only SELECT is allowed, CTEs are supported, results are capped at max_rows, and truncated: true is returned for larger results. It also names affected tables, giving the agent a clear behavioral model beyond the annotation.

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 compact and front-loaded with the essential action and constraints. Every sentence contributes meaningful operational detail: the SQL requirement, rejection of non-SELECT, row limits, truncation behavior, and table names. There is no redundancy or filler.

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 raw SQL tool with no output schema, the description covers what an agent needs to know to invoke it correctly: supported statements, syntax features, result limits, truncation signaling, and available tables. The read-only annotation covers safety, so no additional behavioral disclosure is necessary.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by specifying that CTEs via WITH ... SELECT are supported and listing the available tables, which helps the agent construct valid SQL statements. It also reinforces the max_rows default and truncation behavior already present in the schema.

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 states a specific verb and resource: 'Execute a raw SQL SELECT query' against the transactions database. It further distinguishes itself from the specialized sibling tools by emphasizing raw SQL and explicitly listing supported tables. The rejection of non-SELECT statements removes ambiguity about what the tool can and cannot do.

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 clearly conveys that this tool is for raw, read-only SQL SELECT queries and provides practical guidance such as using aggregates or LIMIT/OFFSET paging for large result sets. It does not explicitly name sibling tools as alternatives, but the 'raw SQL' framing and rejection of non-SELECT statements establish a clear use context.

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