Skip to main content
Glama

Banco MCP

by io.github.douglac

openfinance_provider_status

Read-onlyIdempotent

Checks the LIVE operational status of the Open Finance provider (its public status page) — this is the PROVIDER's health, separate from your own connection's openfinance_get_item_status. Use it whenever data looks incomplete or stale even though a connection shows UPDATED (accounts/transactions/balances missing, a bank not returning everything): it reveals an upstream outage or a known incident on a specific bank/connector, so you can tell a provider-side problem apart from a connection that just needs reconnecting. Returns the global indicator (none/minor/major/critical), degraded components, open incidents, and — when you have banks connected — flags the incidents that affect YOUR connected banks in your_banks_affected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context by detailing what the tool returns (global indicator, degraded components, open incidents, and `your_banks_affected`) and explaining how to interpret the results, going beyond the annotations.

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 a single, dense paragraph that includes all necessary information without fluff. Although somewhat long, every sentence serves a purpose, covering purpose, usage context, and return values. It is well-structured and 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?

Despite having no output schema, the description explicitly lists the return fields and explains how to use them. It also addresses the tool's role relative to sibling tools and provides a clear decision framework for when to use it. The description is comprehensive for the tool's simplicity.

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 tool has zero parameters, so the input schema is empty. The description does not need to explain parameters. It compensates by clearly explaining the tool's output and its relevance, meeting the baseline for parameterless tools.

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 the tool checks the LIVE operational status of the Open Finance provider's public status page, distinguishing it from the connection-specific `openfinance_get_item_status`. It uses a specific verb and resource, leaving no ambiguity about its purpose.

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 explains when to use this tool (when data appears incomplete/stale despite an updated connection) and contrasts it with `openfinance_get_item_status`, effectively guiding the user to choose the correct tool. It also states the practical benefit of distinguishing provider-side problems from connection issues.

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

All Banco 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.4/5.0
Disambiguation4/5

Each tool targets a specific resource/action (balance, transactions, bills, loans, investments, connections, categories, provider status), with clear boundaries. Minor overlap exists between openfinance_list_transactions and openfinance_list_transactions_by_item, and among the multiple account-related tools, but the descriptions are detailed enough to disambiguate.

Naming Consistency4/5

Almost all tools follow an openfinance_<verb>_<noun> snake_case pattern (list_accounts, get_credit_card_bill, update_transaction_category). Minor deviations include openfinance_provider_status (noun_noun) and openfinance_list_transactions_by_item (extra preposition), but the overall convention is predictable and consistent.

Tool Count4/5

19 tools is on the heavier side but fits the broad scope of an Open Finance banking integration covering connections, accounts, transactions, credit cards, loans, investments, and provider health. Each tool appears justified; the count does not feel bloated.

Completeness5/5

The surface covers the full lifecycle: connection discovery/search/list/sync/disconnect/status, account and transaction retrieval, credit card bill summaries and detail, loans, investments, transaction categorization, and provider diagnostics. No critical dead ends are apparent for the stated banking data domain.

Resources