finance

Accounts: List accounts

list_accounts

Read-onlyIdempotent

    List all financial accounts for the user.

    Args:
        account_type: Filter by type (checking, savings, credit_card, loan, investment, other)
        include_hidden: Include hidden accounts (default: False)
        limit: Maximum number of accounts to return (default: 50, max: 200).
        offset: Number of accounts to skip for pagination (default: 0).

    Returns:
        Dictionary with a paginated accounts list (``total_count`` /
        ``has_more`` / ``offset`` / ``limit``) and a ``summary`` that
        reflects ALL active accounts — household-wide, regardless of the
        page AND of ``account_type`` (its net_worth is the real net
        worth in every case). With ``account_type`` set, ``filtered_subtotal`` adds the
        count and total balance of the matching active accounts. Debt
        accounts include Plaid enrichment: is_overdue, balance_status,
        loan_status, next_payment_due_date.

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

Name	Required	Description	Default
`limit`	No
`offset`	No
`account_type`	No
`include_hidden`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With read-only annotations already covering safety, the description adds substantial behavioral context: pagination fields (total_count, has_more, offset, limit), a summary that is household-wide regardless of page or account_type, filtered_subtotal behavior, and debt-account Plaid enrichment fields. This goes well beyond what annotations provide.

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 front-loaded with a one-line purpose, then structured Args and Returns sections. Every sentence is relevant given the lack of an output schema and the need to document parameters explicitly.

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 four-parameter read-only list tool with no output schema, the description is complete: it explains parameters, return structure, pagination, summary semantics, and debt enrichment. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so completely. It documents account_type allowed values, include_hidden default, limit default and max, and offset default, adding meaning not present in the raw schema.

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 states a specific verb and resource: 'List all financial accounts for the user.' It is clear what the tool does, but it does not explicitly distinguish itself from account-related siblings such as list_shared_accounts or get_account_details.

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 the statement 'List all financial accounts for the user,' and the Args section clarifies filtering options. However, there is no explicit guidance on when to use this tool versus alternatives like list_shared_accounts or get_account_details.

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

All finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?