Quicken Mac MCP

Overview Schema Source Related Servers Discussions Admin

raw_query

Run read-only SQL SELECT queries against the Quicken database for custom analysis beyond built-in tools, with results capped at 500 rows.

Instructions

Execute an arbitrary read-only SQL query against the Quicken database. Only SELECT statements are allowed. Results limited to 500 rows. Use this for custom analysis not covered by other tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sql": "<sql>"
    },
    "name": "raw_query"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	Yes	SQL SELECT query to execute

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses read-only semantics, a SELECT-only restriction, and a hard 500-row cap. It stops short of timeout behavior, whether the connection is isolated, or what error surfaces on a non-SELECT, leaving a modest gap for a tool that executes agent-authored SQL.

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, each doing distinct work: what it does, the safety constraint, the row cap, then the routing hint. Front-loaded and zero filler.

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 a one-parameter escape-hatch tool with no output schema, the description covers the constraints an agent most needs before calling. What it doesn't cover is that the agent must know the underlying table/column schema to form a valid query, which is a real prerequisite left implicit.

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?

Single required 'sql' parameter is fully documented in the schema, so baseline is 4. The description reinforces this with the SELECT-only constraint, which meaningfully narrows what the parameter may contain beyond the schema's plain 'SQL SELECT query' text.

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?

States a specific verb and resource ('Execute an arbitrary read-only SQL query against the Quicken database') and scopes it as an escape hatch for work the curated tools don't cover. An agent can distinguish it from spending_by_category or list_accounts without opening any schema.

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?

'Use this for custom analysis not covered by other tools' clearly establishes it as the fallback when the purpose-built siblings fall short. It does not name which sibling to try first or warn about when a targeted tool is preferable, but the routing intent is unambiguous.

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

Deploy Server