Skip to main content
Glama

Santander 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 the readOnly/idempotent annotations by explaining the snapshot semantics, the meaning of updateDateTime/updatedAt, the two credit-specific error modes, the degraded row behavior with realtime:false, and the non-throwing warning mechanism. It also discloses the exact response shape. This is exemplary behavioral disclosure for an agent.

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 the essential purpose and progressively covers caveats, error modes, and response shape. Every sentence adds operational value; none repeats annotation data. The length is justified by the tool's complexity and the absence of an output schema.

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 the tool's complexity, single parameter, no output schema, and rich sibling ecosystem, the description is fully sufficient. It covers freshness semantics, error/consent issues, degraded fallback behavior, sync guidance, and response shape, leaving no critical decision unclear to an agent.

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 schema only says account_ids is a required array of strings; with 0% schema description coverage, the description must compensate. It does so by specifying 'Pass `account_ids` as an array (1–50)' and linking the parameter to account-level balance retrieval. This is enough for correct invocation, though a bit more detail about duplicate or unknown IDs would be even stronger.

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 precise statement of the operation: 'Returns the latest available balance per account id.' It names the REST endpoint and immediately differentiates the result from a live reading, so an agent knows exactly what resource it is asking for. The tool is clearly distinct from sibling list/read tools such as openfinance_list_transactions and openfinance_get_accounts_detail.

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?

The description explicitly addresses when to use this tool and what to do instead when results are stale: if recent movements are missing or the balance disagrees with openfinance_list_transactions, the agent should run openfinance_force_sync and then re-read. It also explains institution-level failure handling, so an agent knows this tool returns warnings rather than throwing in specific scenarios.

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

All Santander 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

A3.9/5.0
Disambiguation3/5

The openfinance_* tools are mostly distinct by resource and action, but several pairs create ambiguity: openfinance_get_item_status vs openfinance_provider_status, openfinance_list_transactions vs openfinance_list_transactions_by_item, and the monolithic marketplace tool overlaps with top-level report_bug and toolkit_info. Descriptions do clarify the differences, but an agent selecting by name alone could easily choose the wrong tool.

Naming Consistency3/5

The openfinance_* family follows a mostly consistent verb_noun pattern (list_accounts, get_balance, update_transaction_category), which is good. However, top-level tools mix bare verbs, nouns, and verb_noun forms (authenticate, connect, marketplace, show_version, toolkit_info), and openfinance_provider_status breaks the verb-first pattern. The naming is readable but not uniform across the whole set.

Tool Count3/5

25 tools sits right at the heavy boundary, though the server covers two domains: mcp.ai platform management and Open Finance data access. Some tools could be consolidated (list_transactions vs list_transactions_by_item, get_item_status vs provider_status), and marketplace is a monolithic super-tool that bundles many sub-capabilities. Overall the count is defensible but slightly bloated.

Completeness4/5

The Open Finance surface is thorough: accounts, balances, transactions, credit card bills, loans, investments, connection management, sync, category updates, and provider health are all covered. Minor gaps exist, such as no investment detail beyond the list and connection actions being URL-based rather than first-class tools, but there are no dead ends for typical read/aggregation workflows.

Resources