Skip to main content
Glama

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

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint and idempotentHint, so no mutation. Description adds details about live nature, public status page, and return values (global indicator, degraded components, open incidents, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured and front-loaded with purpose and differentiation. It is slightly lengthy but every sentence adds value. No wasted words, though could be tightened slightly.

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 simple read tool with no output schema, the description fully explains what it does, when to use it, and what it returns. No gaps remain.

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?

Tool has zero parameters and schema coverage is 100%, so description cannot add value there. Baseline 4 is appropriate as it is not required to elaborate further.

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?

Description clearly states the tool checks the LIVE operational status of the Open Finance provider, distinct from the connection status. It provides a specific verb ('Checks') and resource ('operational status of the Open Finance provider') and explicitly distinguishes from the sibling tool `openfinance_get_item_status`.

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?

Explicitly tells when to use: when data looks incomplete or stale despite a connection showing UPDATED. It contrasts with the connection status tool, giving clear diagnostic context. No ambiguity about the intended use case.

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

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

The openfinance_* tools are cleanly separated by resource and action (accounts, transactions, bills, investments, loans, connections), and the list-versus-get patterns are distinguishable. The main weak spots are the broad 'marketplace' tool, which bundles many sub-actions, and mild overlap between list_accounts/get_account_balance and list_transactions/list_transactions_by_item.

Naming Consistency4/5

The banking tools follow a consistent openfinance_<verb>_<noun> convention, with list_/get_ prefixes used predictably. A few deviations like 'provider_status' (missing a verb) and non-prefixed platform tools (authenticate, connect, marketplace, toolkit_info) keep it from being perfectly uniform.

Tool Count4/5

25 tools is on the heavy side, but the Open Finance domain justifies a wide surface: balances, transactions, bills, investments, loans, connections, sync, and provider health each need their own entry points. The platform/meta tools add some bulk but are individually useful.

Completeness5/5

The Open Finance surface covers the full read lifecycle: discover/search connectors, connect via URLs, list and inspect connections, force sync, check provider/connection status, and read accounts, balances, transactions, credit card bills, investments, and loans. It also supports the one clearly expected write operation (transaction category correction), leaving no obvious dead ends in the core domain.

Resources