Skip to main content
Glama

Crefisa 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. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true, and the description adds context about what it does (returns global indicator, degraded components, open incidents, affected banks), with no contradiction.

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 well-structured and front-loaded with the main purpose, but slightly long with extra details; every sentence adds value, though it could be more concise.

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 and no output schema, the description fully explains the tool's purpose and return values (global indicator, degraded components, incidents, affected banks), making it completely understandable.

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?

No parameters in the schema, so baseline is 4. The description adds no parameter info as none exist, but compensation is unnecessary due to zero parameters.

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, distinguishes it from the user's connection status via openfinance_get_item_status, and specifies the verb 'Checks' and resource '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 this tool: when data looks incomplete or stale even though a connection shows updated, and differentiates between provider-side problems and connection issues, providing clear context for decision-making.

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

All Crefisa 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/5.0
Disambiguation3/5

Most open_-finance tools are clearly bound to a resource+action, but several pairs require careful reading: list_transactions vs list_transactions_by_item, get_iate_status vs get_provider_status, and connect vs list_connections. The marketplace tool is also a single heavily overloaded tool that bundles search/describe/invoke/install and a prompt library, which blurs its boundary.

Naming Consistency4/5

The Open Finance tools follow openfinance_verb_noun consistently, and the top-level tools are all snake_case, so there is no wild con convention mixing. Deviations exist in generic tools like marketplace/toolki_i/nfo and in non-verb patterns like accent_status, but overall the naming is readable and predictable.

Tool Count3/5

At 25 tools the server sits at the upper edge of what is comfortably scoped; the many list/get/status endpoints are justified by the Open Finance domain, but the extra marketplace and admin utilities make it feel broader than a single-purpose sovereign. It is not abusive, but it is definitely on the heavy side.

Completeness4/5

The Open Finance access covers accounts, balances, transactions, credit card bills, investment, loans, connections, diagnostics, force-sync, and transaction recategorization. Missing operations are mostly intentional autentications/connection widget hand-offs (add_connection_url, reconnect_url), so the set can still support common workflows without dead ends.

Resources