Skip to main content
Glama

Conta Bemol 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.9/5.0
Behavior5/5

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

Annotations provide readOnlyHint, idempotentHint, and destructiveHint. The description adds significant behavioral details beyond annotations: it states the tool checks a public status page, returns global indicator, degraded components, open incidents, and flags incidents affecting connected banks via `your_banks_affected`. No contradictions.

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 three sentences long, each packing useful information. It is front-loaded with the main purpose. However, it could be slightly more concise; for example, the explanation of 'your_banks_affected' could be integrated more succinctly.

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 has no parameters and no output schema, the description completely covers what the tool does, when to use it, and what it returns (global indicator, degraded components, incidents, affected banks). It provides sufficient context for an agent to select and invoke it correctly.

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?

There are zero parameters, so the input schema offers no semantics. The description fully explains what the tool does without needing to describe parameters, meeting the baseline for no-parameter tools. It adds rich context about the tool's output and use cases.

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 uses the specific verb 'Checks' and identifies the resource as 'LIVE operational status of the Open Finance provider'. It clearly distinguishes this tool from the sibling `openfinance_get_item_status`, which checks the connection's own status, not the provider's health.

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 states when to use: 'whenever data looks incomplete or stale even though a connection shows UPDATED'. It explains the tool reveals upstream outages or known incidents, helping differentiate provider-side problems from connection issues. It also contrasts with the sibling tool `openfinance_get_item_status`.

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

All Conta Bemol 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.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose: accounts, transactions, credit card bills, loans, investments, connections, sync, categories, provider status, and platform meta-tools are all separable. Even the two transaction tools differ (per-account list vs consolidated analysis) and the two status tools differ (connection vs provider health).

Naming Consistency4/5

The openfinance_* prefix is consistently applied across the financial domain, and most follow a verb_noun pattern (list_accounts, get_balance, update_category). However, there are non-prefixed tools (authenticate, connect, marketplace, toolkit_info) and one outlier like openfinance_provider_status (noun instead of verb) that slightly break the pattern.

Tool Count3/5

25 tools is at the upper boundary of what feels heavy for a single server, even for a comprehensive financial aggregation toolkit. The number is justified by the breadth of domains covered (accounts, credit, loans, investments, connections, platform features), but it requires careful agent selection and might be better split into separate servers.

Completeness5/5

The surface covers the full financial data lifecycle: listing and fetching details for all asset types, updating transaction categories, managing connections (list, sync, disconnect, reauth), checking provider health, and searching connectors. There are no obvious dead ends—every domain has read and appropriate write/update operations.

Resources