Skip to main content
Glama

Banco PAN 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 indicate readOnly, idempotent, non-destructive. Description adds valuable behavioral context: it returns global indicator, degraded components, open incidents, and flags affected banks. No contradiction with annotations; description enriches transparency.

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?

Two sentences, front-loaded with main purpose, then usage guidelines, then return details. The second sentence is somewhat long but packs necessary information. Could be split for readability, but overall efficient.

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 explains the return value and how it distinguishes provider issues from connection issues. It also lists sibling tools and differentiates itself, providing complete context.

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 input schema (0 params), so baseline is 4. The description correctly does not add parameter information since none exist. Schema coverage is 100% trivially.

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 LIVE operational status of the Open Finance provider, distinguishing it from sibling openfinance_get_item_status, which checks your own connection. The verb 'checks', resource 'Open Finance provider', and explicit separation from the sibling tool provide exceptional purpose clarity.

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 also explains the alternative openfinance_get_item_status and provides a clear decision rule (provider-side problem vs connection issue). This is exemplary guidance.

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

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

The tools are mostly distinct, covering authentication, marketplace navigation, Open Finance data retrieval (accounts, transactions, bills, loans, investments), and status/connector management. Some overlap exists between openfinance_list_transactions and openfinance_list_transactions_by_item (both return transactions, but the latter is a consolidated summary), which could cause momentary confusion, though descriptions clearly differentiate them.

Naming Consistency4/5

Tool names follow a clear pattern: 'openfinance_' prefix for Open Finance operations, with consistent verb_noun structure (list_accounts, get_account_balance, update_transaction_category). However, there are a few outliers like 'authenticate', 'connect', 'marketplace', 'report_bug', and 'show_version' that don't follow the Open Finance naming convention, though they serve different purposes and are still readable.

Tool Count4/5

With 25 tools, the count is slightly high but justifiable given the broad scope: the server covers Open Finance banking data (accounts, transactions, bills, loans, investments, connections), marketplace operations, and system utilities. Not all tools are used in every session, but each serves a distinct purpose, and the count remains manageable due to clear grouping.

Completeness4/5

The tool surface covers the core Open Finance lifecycle well: list and get accounts, transactions, bills, loans, investments, plus sync, reconnect, and category updates. It also includes connector search and provider status. Minor gaps exist, such as no explicit tool for updating or deleting a transaction category rule, and no direct CRUD for connections (only list and disconnect), but these are acceptable gaps.

Resources