Skip to main content
Glama
Sign In
Quicken Mac MCP

Quicken Mac MCP

by dweekly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_accounts

Retrieve all Quicken accounts with name, type, and active/closed status, or filter by account type to locate specific accounts.

Instructions

List all Quicken accounts with name, type, and active/closed status. Optionally filter by account type (case-insensitive).

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

Input Schema

NameRequiredDescriptionDefault
account_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does add useful context beyond the name: the returned fields (name, type, active/closed status) and the case-insensitive filter behavior. However, it omits auth requirements, ordering, pagination, and whether closed accounts are included by default.

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?

Two short sentences with zero filler. The primary behavior is front-loaded and the optional filter detail follows, so an agent can read it in one pass.

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 single-parameter read-only list tool with no output schema and no annotations, the description supplies the essential return fields and filter semantics. Only minor details such as ordering, pagination, or default inclusion of closed accounts are 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?

Schema coverage is 0% and the single parameter is only typed as 'string', so the description does the work: it states the parameter is optional, filters by account type, and is case-insensitive. It stops short of listing valid account type values, which would have completed the picture.

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?

The description names a specific verb and resource ('List all Quicken accounts') and enumerates the returned fields (name, type, active/closed status), so the agent knows exactly what this tool produces. It does not explicitly distinguish itself from siblings like query_transactions or raw_query, keeping it at a 4 rather than a 5.

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?

Usage is implied by 'List all... accounts' and the optional type filter, but there is no explicit statement of when to prefer this over query_transactions or raw_query for account data. The filtering guidance is present but no exclusions or alternatives are given.

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