Skip to main content
Glama

Banco PAN 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, but the description adds substantial behavioral context beyond those: the balance is a snapshot anchored to the last upstream sync, rows include updateDateTime/updatedAt as the sync instant, credit accounts may return structured warnings instead of throwing, and upstream 5xx or non-Open Finance connectors degrade the row. This is precisely the kind of non-obvious runtime behavior an agent needs.

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 every sentence adds necessary operational context: endpoint, freshness semantics, sync remedy, error behavior, and degraded responses. The main action is front-loaded and supporting details are ordered logically.

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 single-parameter read-only tool with no output schema, the description covers what the agent needs to know: how to invoke it, what the semantics of the response are, what to do in stale-data situations, and how errors/warnings are represented. Nothing essential 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 coverage is 0%, so the description carries the full burden for the single parameter. It explains that account_ids must be passed as an array, supports 1 to 50 items, and that the balance is returned per account id. This meaningfully exceeds the bare schema definition.

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 names a specific verb (Returns), a specific resource (latest available balance per account id), and the exact endpoint (GET /accounts/:id/balance). It also clearly distinguishes the tool's snapshot semantics from a live read, which separates it from transaction or 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 tells the agent when to use this tool for the freshest available balance and when not to trust it, and it names the alternative: if data is stale or inconsistent with transactions, run openfinance_force_sync and re-read. It also explains how credit account errors should route behavior (reconnecting the bank restores consent).

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

All Banco PAN 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

The tools are mostly distinct, covering authentication, marketplace navigation, Open Finance data retrieval (accounts, transactions, bills, loans, investments), and status/connector management. Some overlap exists between openfinance_list_transactions and openfinance_list_transactions_by_item (both return transactions, but the latter is a consolidated summary), which could cause momentary confusion, though descriptions clearly differentiate them.

Naming Consistency4/5

Tool names follow a clear pattern: 'openfinance_' prefix for Open Finance operations, with consistent verb_noun structure (list_accounts, get_account_balance, update_transaction_category). However, there are a few outliers like 'authenticate', 'connect', 'marketplace', 'report_bug', and 'show_version' that don't follow the Open Finance naming convention, though they serve different purposes and are still readable.

Tool Count4/5

With 25 tools, the count is slightly high but justifiable given the broad scope: the server covers Open Finance banking data (accounts, transactions, bills, loans, investments, connections), marketplace operations, and system utilities. Not all tools are used in every session, but each serves a distinct purpose, and the count remains manageable due to clear grouping.

Completeness4/5

The tool surface covers the core Open Finance lifecycle well: list and get accounts, transactions, bills, loans, investments, plus sync, reconnect, and category updates. It also includes connector search and provider status. Minor gaps exist, such as no explicit tool for updating or deleting a transaction category rule, and no direct CRUD for connections (only list and disconnect), but these are acceptable gaps.

Resources