Skip to main content
Glama

Toro MCP

by io.github.mcp-dir

openfinance_get_account_balance

Read-onlyIdempotent

Returns the latest available balance per account id (GET /accounts/:id/balance). This is the freshest balance the provider can serve, but it is a SNAPSHOT anchored to the connection's last upstream sync: the updateDateTime/updatedAt in each row is that sync instant, NOT a to-the-second live read. If a movement that just happened is not reflected yet, or the balance disagrees with the sum of openfinance_list_transactions, run openfinance_force_sync to pull fresh data and then re-read. Pass account_ids as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR (provider could not fetch it) or BALANCE_CONSENT_ERROR (the institution refused it because the consent lacks the balance permission — reconnecting the bank restores it) — those rows include a structured warning instead of throwing. When the financial institution is temporarily unavailable upstream (5xx) or the connector is not Open Finance, the row DEGRADES to the last-synced balance with realtime: false, updatedAt and a warning instead of an error. Response shape: { results: [...], errors: [{ id, status, message }] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idsYes

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond annotations, disclosing that updatedAt is the sync instant rather than a live read, that errors may be embedded as warnings, and that rows can degrade to last-synced balances with realtime:false. Nothing is hidden.

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 long but dense, front-loading the core behavior and then layering necessary caveats about freshness, errors, and degradation. Every sentence adds actionable information rather than padding.

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?

With no output schema, the description supplies the response shape, error structure, degraded behavior, and parameter constraints. It fully equips an agent to call the tool and interpret results correctly.

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?

Although schema coverage is 0%, the description compensates by stating that account_ids must be an array with 1–50 items. It doesn't spell out where the account IDs come from, but for a single parameter this is enough to invoke correctly.

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 opens with a specific verb and resource: 'Returns the latest available balance per account id', and cites the endpoint. This clearly distinguishes the tool from list/transaction/sync siblings.

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

Usage Guidelines5/5

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

It explicitly explains the snapshot nature, tells the agent to call openfinance_force_sync if data seems stale or disagrees with openfinance_list_transactions, and describes degraded responses. This gives concrete when-to-use and when-to-use-alternative guidance.

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

All Toro 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.1/5.0
Disambiguation4/5

Each Open Finance resource has a clearly named list/get pair, and connection status vs provider status vs force sync are distinct. The main ambiguity is between list_accounts (which already carries balances) and get_account_balance, and between list_transactions and list_transactions_by_item, which requires reading the descriptions carefully.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (list_*, get_*, update_*, force_sync, search_*). Exceptions like marketplace, toolkit_info, and openfinance_provider_status break the pattern slightly, but the two logical groups are predictable internally.

Tool Count3/5

At 25 tools this is on the heavy end of the scale. Most tools have a real purpose, but several list/get pairs and the multi-purpose marketplace mega-tool could be consolidated without losing functionality, making the overall surface feel larger than strictly necessary.

Completeness4/5

The Open Finance surface is impressively broad: connections, accounts, balances, transactions, credit-card bills, loans, investments, categorization, sync, provider health, and connector search are all covered. Minor gaps like a single-transaction getter or a consolidated statement export force agents to assemble data with extra calls, but no critical workflow is blocked.

Resources