Skip to main content
Glama

Neon 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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint; the description adds behavioral context about what the tool returns (global indicator, degraded components, incidents) and how it flags incidents affecting connected banks, going beyond the 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?

The description is well-structured with purpose first, then usage guidance, then return details. It is slightly verbose but every sentence adds value; could be tightened slightly without loss.

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 zero-parameter tool with no output schema, the description fully covers purpose, usage context, return data, and how it helps diagnose provider-side problems. It is complete and actionable.

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 in the schema, so baseline 4 applies per guidelines. The description adds no parameter information, which is appropriate given zero parameters and 100% schema coverage.

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, explicitly distinguishing it from the sibling tool openfinance_get_item_status by explaining the provider health vs. connection status difference.

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?

The description provides explicit guidance on when to use this tool: when data looks incomplete or stale even though a connection shows UPDATED, and it names the alternative openfinance_get_item_status for connection-level issues.

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

All Neon 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

A3.9/5.0
Disambiguation4/5

The openfinance_* family is cleanly separated by resource and action, and tricky pairs like list_accounts vs get_account_balance and list_transactions vs list_transactions_by_item are explicitly cross-referenced in descriptions. However, marketplace bundles a large set of sub-actions, and connect/toolkit_info partially overlap on reporting connection state, so a couple of boundaries are fuzzy.

Naming Consistency4/5

The openfinance_* tools consistently follow a verb_resource pattern with snake_case, which is highly predictable. The generic platform tools mostly fit the same style, but marketplace and toolkit_info are noun-only names, and openfinance_provider_status also breaks the verb pattern, so it is not perfectly uniform.

Tool Count3/5

At 25 tools, this server falls at the heavy end of the borderline range. The many openfinance_* list/get tools are individually justified for the financial domain, but adding platform tools like marketplace, connect, toolkit_info, and show_version makes the overall surface larger than a minimal server needs.

Completeness5/5

The financial surface is remarkably thorough: accounts, transactions, credit card bills, loans, investments, categories, connection lifecycle, sync, and provider health are all covered with list/get and update paths where applicable. The platform side also covers auth, connection status, marketplace discovery/execution, versioning, and bug reporting, leaving no obvious dead ends.

Resources