Skip to main content
Glama

Banco BRB MCP

by io.github.mcp-dir

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

Schema Changelog

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

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context: it reveals upstream outages, returns global indicator, degraded components, open incidents, and flags affected banks. No contradiction with annotations.

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 a single, well-structured paragraph of about 60 words. It starts with the core purpose, then usage guidelines, then details of what it returns. Every sentence adds value with no redundancy.

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 parameters, good annotations, and no output schema, the description fully explains what the tool returns (global indicator, components, incidents, your_banks_affected) and when to use it. It is complete for a read-only status check tool.

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 input schema has zero parameters (100% coverage), so there is nothing to describe. Baseline for zero parameters is 4; no additional information is needed.

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 checks the LIVE operational status of the Open Finance provider's public status page, distinguishing it from openfinance_get_item_status. The verb 'Checks' and resource 'provider status' are specific and unambiguous.

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 states when to use this tool: 'whenever data looks incomplete or stale even though a connection shows UPDATED' and contrasts it with openfinance_get_item_status, telling the agent to use it to differentiate 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 BRB 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
Disambiguation4/5

Most openfinance_* tools map cleanly to distinct resources and actions, and the list/get split is readable. The main risk is openfinance_list_transactions vs openfinance_list_transactions_by_item, which both return transactions and could be confused; openfinance_get_item_status vs openfinance_provider_status also sound similar, though descriptions clarify them.

Naming Consistency4/5

The openfinance_* family follows a consistent openfinance_<verb>_<noun> pattern, and platform tools mostly use simple verb_noun names. Deviations include openfinance_list_transactions_by_item, which breaks the noun pattern, and the non-prefixed platform tools (authenticate, connect, marketplace) mixing in a second naming category.

Tool Count3/5

At 25 tools, this is at the high end of reasonable scope. The open finance data surface is genuinely broad, so most tools earn their place, but the marketplace/platform tools effectively add a second unrelated domain and push the set toward heavy.

Completeness4/5

The open finance lifecycle is well covered: connection search, sync, status, disconnect, accounts, balances, transactions, credit card bills, loans, investments, and category correction. Minor gaps exist (no single-transaction fetch, no connection update beyond force_sync), but core agent workflows do not hit dead ends.

Resources