Skip to main content
Glama

Itaú 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 provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's main value is in adding behavioral context. It details the return fields: global indicator, degraded components, open incidents, and a 'your_banks_affected' flag. No contradictions with 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 moderately long but well-structured: first sentence states the purpose, second explains usage guidance and what it reveals, third lists return values. Every sentence adds value, though the third could be slightly more concise without losing information.

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 output schema, the description adequately explains the return values (global indicator, degraded components, open incidents, your_banks_affected). It is complete for an agent to understand what to expect and how to use the 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?

The input schema has zero parameters and 100% schema description coverage. With no parameters, a baseline of 4 is appropriate. The description does not need to add parameter info, and it correctly omits it.

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's public status page. It distinguishes itself from the sibling tool 'openfinance_get_item_status' by specifying that it checks provider health, not the user's own connection.

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 explicitly tells when to use the tool: when data looks incomplete or stale despite a connection showing UPDATED, and when accounts/transactions/balances are missing. It contrasts with 'openfinance_get_item_status' and explains that it reveals upstream outages or known incidents.

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

All Itaú 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

The Open Finance tools have clear list/get pairs for each resource (accounts, transactions, loans, investments, bills), but the marketplace tool is a monolith combining search, describe, invoke, install, subscribe, and prompt library actions, causing ambiguity about which action to use. Additionally, openfinance_list_transactions and openfinance_list_transactions_by_item overlap in purpose but are distinguished by scope.

Naming Consistency3/5

The openfinance_* group follows a consistent verb_noun pattern (list, get, update, force_sync, etc.), but the platform tools (authenticate, connect, marketplace, show_version, report_bug, toolkit_info) use mixed bare verbs and nouns, creating two distinct conventions. Names like openfinance_list_transactions_by_item are longer but still consistent within the group.

Tool Count4/5

25 tools is at the heavy end, but the Open Finance domain alone justifies 17 tools covering distinct resources and operations. The platform tools add 8 more, though the marketplace tool bundles many sub-actions into one, inflating the effective count. The number is borderline but not excessive given the breadth of banking functionality.

Completeness5/5

The Open Finance surface is comprehensive with list/get for every major resource, plus support for sync, status, search, categories, and category updates. The platform tools cover authentication, connection status, marketplace operations, bug reporting, version, and toolkit state. No obvious gaps or dead ends in the workflow.

Resources