Skip to main content
Glama

Íon 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. First observed

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, destructiveHint=false. Description adds context about accessing public status page, returning global indicator, degraded components, incidents, and 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?

Single paragraph with high information density; covers purpose, usage, and return details. Slightly verbose but well-structured and front-loaded.

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 no output schema, description lists all relevant return values (global indicator, degraded components, incidents, your_banks_affected). Sufficient for a 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?

No parameters, schema coverage 100%. Description does not need to explain parameters. Baseline 4 for zero-param tool.

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?

Clearly states it checks the Open Finance provider's LIVE operational status, distinguishing from openfinance_get_item_status. Specific verb 'Checks the... operational status' and resource 'Open Finance provider'.

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 says when to use: when data is incomplete/stale despite connection showing UPDATED, and provides specific scenarios (accounts/transactions missing). Distinguishes from 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 Íon 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.1/5.0
Disambiguation5/5

Each openfinance tool targets a distinct resource/operation (accounts, transactions, bills, loans, investments, connections, categories, sync, status), and the non-openfinance tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are clearly separate. The only near-overlap is between openfinance_list_transactions and openfinance_list_transactions_by_item, but the latter explicitly handles whole-connection consolidation and the descriptions clarify when to use each.

Naming Consistency5/5

All openfinance tools share the `openfinance_` prefix with a consistent verb_noun pattern (list_, get_, update_, force_sync, provider_status, search_). Non-openfinance tools use simple imperative verbs (authenticate, connect, report_bug, show_version) and the noun-phrase toolkit_info, all consistent in style with no mixed conventions.

Tool Count4/5

25 tools is on the high side, but each serves a distinct function within the comprehensive Open Finance domain (accounts, transactions, bills, loans, investments, connections, categories, sync, status) plus general server utilities. The count is justified by the breadth of the domain, though it exceeds the typical 3-15 range.

Completeness4/5

The surface covers the full read lifecycle for financial data: listing and detail for accounts, transactions, bills, loans, investments, plus connection management (list, disconnect, force_sync), categories, and provider status. Missing write operations like transfers are likely out of scope, and minor gaps such as no separate 'get investment' detail are acceptable since list_investments returns comprehensive data.

Resources