Skip to main content
Glama

Necton 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.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds detailed behavioral context: it checks a public status page, returns global indicator, degraded components, incidents, and flags affecting connected banks. 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.

Conciseness5/5

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

The description is a single well-structured paragraph, front-loaded with the main purpose, and packs significant detail without verbosity.

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, the description fully explains the return values: global indicator, degraded components, open incidents, and affected banks. Complete 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 exist, so schema coverage is trivially 100%. Baseline is 4. The description does not need to add parameter semantics.

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 the tool checks the LIVE operational status of the Open Finance provider, using specific verbs and distinguishing it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use this tool (when data looks incomplete or stale despite updated connection), and what it differentiates. It lacks an explicit 'when not to use' but provides strong contextual guidance.

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

All Necton 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
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., force_sync vs get_item_status, list_accounts vs get_accounts_detail). Minor overlap exists between list_transactions and list_transactions_by_item, and between get_account_balance and list_accounts (which also contains balance), but descriptions clarify when each should be used.

Naming Consistency4/5

All openfinance_* tools follow a consistent snake_case verb_noun pattern (list, get, force_sync, disconnect, update). The generic tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are also lowercase with underscores where needed, though they lack the openfinance prefix. No mixing of camelCase or chaotic patterns, so mostly consistent with minor deviation.

Tool Count3/5

25 tools is on the heavy side for a single server, but justified given the breadth of Open Finance operations (accounts, transactions, bills, loans, investments, connections, categories, provider status). The count is borderline heavy but not excessive for the domain, though some consolidation could be possible (e.g., merging get_account_balance into list_accounts).

Completeness5/5

The tool surface covers the full lifecycle for financial data: listing, getting details, forcing syncs, disconnecting, updating categories, checking provider status, and handling investments/loans/bills. No obvious dead ends; even connection management includes search, connect URLs, and re-authentication flows. The set appears comprehensive for its intended purpose.

Resources