Skip to main content
Glama

Clear MCP

by io.github.mcp-dir

openfinance_list_accounts

Read-onlyIdempotent

Returns accounts for a bank connection: BANK (checking/savings) and CREDIT (credit card) with balance, number, type, subtype, bankData, and creditData. Also returns bank (the brand/connector name like 'Nubank Empresas' — same shown in the dashboard UI) and connector_id. Note: each account's name is the legal entity that issues the account (e.g. 'Nu Pagamentos S.A. - Instituição de Pagamento'), which is not the same as the brand — when referring to the bank in user-facing text, use bank. OMIT item to list accounts across ALL linked banks at once — the response aggregates every connection's accounts into results, each row tagged with its own bank/connector_id/item_id (use this when the user asks for 'my accounts/cards' without naming a bank). Pass item to target a single bank (response carries bank/connector_id/item_id at the root). CREDIT (credit card) balance: its meaning is CONNECTOR-DEPENDENT — some banks report the current open-bill partial, others the full revolving/installment debt — so do NOT treat balance as 'this month's bill'. The open billing cycle is defined by creditData.balanceCloseDate (when it closes) / balanceDueDate (when it's due). For a standardized open-bill amount and total debt that mean the same across connectors, use openfinance_list_credit_card_bills (open_bill + total_pending_debt, derived from PENDING transactions); closed bills come from that same tool's results. A CREDIT row may carry creditData.usedAmount (how much of THIS card's limit the bank reports as consumed) and a balance_notice. balance_notice means balance came back 0,00 while the bank's own payload indicates an outstanding amount — some issuers never fill the card's consolidated balance field. When it is present, do NOT tell the user the card has nothing to pay: read the amount from openfinance_list_credit_card_bills instead. bankData.closingBalance and automaticallyInvestedBalance are provider-reported extras that can LAG right after a connection is first created: the bank may publish the connection as UPDATED before those derived fields converge, so they can briefly carry a stale/phantom value that a force sync (openfinance_force_sync) reconciles. The account's own balance is authoritative — treat those two as hints until they agree with it. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a bank in this response: balances and credit limits may be unreliable (incomplete or wrong, e.g. a credit limit near 1,00) even with the connection UPDATED, until the provider recovers. Do not present those values as real. May include an identity_notice when the SAME account (same number) arrives via two connections stamped with DIFFERENT owner/taxNumber: in Open Finance those fields reflect each connection's CONSENT HOLDER (e.g. a joint account consented by both holders), so dedupe by account number before summing balances and do not attribute ownership by owner/taxNumber for those accounts.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNo
typeNo
item_idNo
item_idsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / item_ids
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  6. Added
  7. Removed
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Even though annotations already mark this as read-only and idempotent, the description goes far beyond that by disclosing connector-dependent balance semantics, the meaning of balance_notice, possibly lagging bankData fields, provider_incident implications, and identity_notice deduplication guidance. This is unusually transparent and contradicts no 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 long, but almost every sentence adds a distinct caveat or routing rule that an agent needs to avoid misinterpreting data. It is front-loaded with the core return shape, though it is a single dense block that could benefit from light structural separation.

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 the tool's complexity and the absence of an output schema, the description covers return fields, bank display names, balance edge cases, incident handling, identity deduplication, and bulk execution. An agent has enough context to select and invoke this tool correctly in nearly all realistic scenarios.

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?

With 0% schema description coverage, the description must carry the parameter documentation, and it does for item (omit vs pass), item_ids, and type by naming BANK/CREDIT. However, the singular item_id parameter is not explicitly explained in the description, leaving a small gap in an otherwise strong compensation effort.

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 opens with a specific verb and resource: it returns accounts for a bank connection, enumerates BANK and CREDIT categories, and lists the returned fields (balance, number, type, subtype, bankData, creditData). It also distinguishes this tool from the related credit-card bill tool by explicitly routing standardized balance needs elsewhere.

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 the agent when to omit item to aggregate all linked banks versus passing item to target a single bank. It also names an alternative tool, openfinance_list_credit_card_bills, for standardized open-bill and total-debt values, making selection criteria clear.

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

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

Tools are mostly distinct, with clear descriptions differentiating them. Some overlap between openfinance_list_accounts and openfinance_get_accounts_detail, but descriptions clarify that one returns summaries and the other full details. The marketplace tool is very detailed and avoids confusion with Open Finance tools.

Naming Consistency3/5

The Open Finance tools follow a consistent openfinance_verb_noun pattern, but other tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) do not use a prefix. This mix of conventions reduces overall consistency, though within the Open Finance subset the pattern is clear.

Tool Count4/5

24 tools is a reasonable count for a platform covering authentication, marketplace, and detailed Open Finance operations. The number is slightly high but each tool has a clear purpose and none seem redundant.

Completeness5/5

The tool set covers the full lifecycle of bank connections: listing accounts, transactions, credit card bills, investments, loans, force syncing, provider status, and category management. The marketplace tool also allows extending functionality. No obvious gaps for the intended financial data domain.

Resources