finance

Accounts: Get account details

get_account_details

Read-onlyIdempotent

    Get detailed information about a specific account.

    Args:
        account_id: The ID of the account to retrieve

    Returns:
        Account details including recent transactions.
        Debt accounts include Plaid enrichment: is_overdue, loan_status,
        has_pmi, has_prepayment_penalty, last_statement_balance,
        next_payment_due_date, last_payment_amount/date,
        ytd_interest/principal_paid, and credit card APR breakdown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds behavioral value by specifying the return shape: recent transactions and conditional Plaid enrichment for debt accounts, which is not present in annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with Args and Returns sections and contains no filler. The Returns list is long but justified by the many debt-account enrichment fields. The core purpose is front-loaded.

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 tool with no output schema, it covers the main return values and debt-account specifics. However, it lacks error behavior and account_id provenance, and could state whether recent transactions are limited in count or date range.

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

Parameters2/5

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

Schema coverage is 0% and the description's Args section only says 'The ID of the account to retrieve,' which adds little beyond the parameter name and type. It does not explain where the ID comes from, validity constraints, or behavior for missing accounts.

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: 'Get detailed information about a specific account.' This clearly distinguishes from list_accounts by requiring a specific account_id. However, it does not explicitly differentiate from other get_* siblings like get_account_health or get_account_history.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as list_accounts, get_account_health, or get_account_history. The description implies usage through the verb, but offers no prerequisites, exclusions, or alternate routing.

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?