Skip to main content
Glama

Rico MCP

by io.github.mcp-dir

openfinance_get_accounts_detail

Read-onlyIdempotent

Returns full account objects including extended creditData (additional cards, limits) per id (GET /accounts/:id). Pass account_ids as an array (1–50). { results, errors } batch shape. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a connected bank: credit limits and balances may be unreliable (e.g. a limit near 1,00) until the provider recovers. Do not present those values as real.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idsYes

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the batch response shape (results, errors), the provider_incident block, and data reliability concerns, which goes beyond the readOnlyHint and idempotentHint annotations. No contradiction.

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 concise with two main sentences and a cautionary note, each sentence earning its place. Front-loaded with the core purpose.

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?

Given no output schema, the description adequately explains the return shape and potential edge cases (provider_incident). It covers the single required parameter and distinguishes from siblings.

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?

The description adds meaning to the single parameter by stating it is an array with 1-50 items, which is not in the schema (coverage 0%). This helps the agent understand constraints.

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 clearly states it returns full account objects with extended creditData per ID, and specifies the batch shape and provider incident warning. This distinguishes it from sibling tools like openfinance_list_accounts which only lists accounts.

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?

Provides guidance on passing account_ids as an array of 1-50 items and warns about unreliable data during provider incidents. However, it does not explicitly state when to use this tool over alternatives like get_account_balance.

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

All Rico MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, especially the openfinance_* family, but there is some overlap: openfinance_list_transactions and openfinance_list_transactions_by_item both cover transaction listing (though the latter is aggregated by connection), and openfinance_get_account_balance vs openfinance_list_accounts both return balance info. Descriptions are detailed enough to guide selection, so ambiguity is limited but present.

Naming Consistency4/5

The 19 openfinance_* tools follow a consistent verb_noun pattern (list_accounts, get_balance, force_sync). The remaining generic tools (connect, authenticate, marketplace, report_bug, etc.) don't share the prefix but use clear verb-style names. Two conventions exist, but within each group naming is predictable and readable.

Tool Count3/5

25 tools is at the high end but supports the dual scope: platform management (connect, auth, marketplace) and comprehensive Open Finance data access (19 tools). The count feels slightly heavy, especially with the massive marketplace tool that bundles many actions into one, but it's justified by the breadth of the financial domain.

Completeness4/5

The Open Finance surface is quite complete: accounts, balances, transactions, bills, loans, investments, categories, connections, sync, and provider status are all covered. Missing minor operations like updating categories is present, but there is no obvious gap like missing update/delete for transactions (not applicable). The platform side is minimal but sufficient for auth and info.

Resources