Skip to main content
Glama

Banco do Nordeste do Brasil MCP

openfinance_get_credit_card_bill

Read-onlyIdempotent

Returns bill-level detail for one or more credit card bills by id (GET /bills/:id): dueDate, billClosingDate (when the cycle closed — the boundary that defines which purchases belong to this bill), totalAmount, financeCharges and payments[] (id, paymentDate, amount, valueType, paymentMode). ITEMIZED PURCHASES (OPT-IN): the bank's bill payload has no transactions in it — they live on the card ACCOUNT. Pass include_transactions:true (plus account_id of the credit card, since the bill itself carries no account reference) and each row also gets transactions[], transactions_count, transactions_sum and reconciles_with_total, already matched to that bill. Always check transactions_basis: bill_id = exact (the bank tagged each transaction with this bill — the normal case for CLOSED bills), date_window = ESTIMATE (confidence:'low', window echoed in transactions_window) used when the connector tags no billId or the bill is still open (PENDING lines get no billId until the cycle closes), unavailable = no link possible. Opt-in because it costs an extra full transaction scan of the account. Whatever the basis, the bill's own totalAmount is authoritative — do NOT rebuild it by summing transactions. Without the opt-in the response carries a transactions_hint; you can also fetch them yourself via openfinance_list_transactions with the credit card account_id and a from/to range ending at billClosingDate. Pass bill_ids as an array — use openfinance_list_credit_card_bills first to discover ids. { results, errors } batch shape. NOTE: Pluggy does NOT return a paid/status field. In Brazilian Open Finance, payments[] reflects payments registered during THIS bill's billing cycle — typically the payment of the PREVIOUS bill (do NOT assume this bill was paid just because payments[] is non-empty). To check paid status, prefer openfinance_list_credit_card_bills which derives payment_status via cross-bill match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bill_idsYes
account_idNo
transactions_detailNo
include_transactionsNo

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds considerable behavioral context beyond that: the extra cost of the transactions opt-in (full transaction scan), the meaning of transactions_basis values (estimate, unavailable), the note that payments[] may reflect the previous bill rather than this one, and that the bill's totalAmount is authoritative. No contradiction with annotations exists.

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 structured with clear paragraphs: primary purpose, opt-in details, transactions_basis explanation, and important caveats. It is front-loaded with the main action and then provides necessary depth. While verbose, each sentence adds value; minor redundancy could be trimmed without losing necessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is highly detailed, listing return fields, batch shape, transactions_basis variants, and critical financial caveats about payments and paid status. However, the undocumented transactions_detail parameter in the schema is never addressed, leaving a potential source of confusion. Given no output schema exists, the description must compensate fully, and this omission prevents a perfect score.

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 coverage, the description carries the burden. It explains bill_ids (array, discover via list), account_id (needed for include_transactions because the bill lacks account reference), and include_transactions (opt-in, adds transactions). However, the transactions_detail parameter is never mentioned, leaving one of four parameters unexplained. Despite this gap, the description provides strong semantics for the other three.

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 starts with a specific verb and resource: 'Returns bill-level detail for one or more credit card bills by id', and lists concrete fields like dueDate, billClosingDate, totalAmount. It explicitly differentiates from siblings by noting that itemized purchases are opt-in and that openfinance_list_credit_card_bills is used to discover ids, and openfinance_list_transactions is an alternative for fetching transactions directly.

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?

It gives explicit instructions: 'use openfinance_list_credit_card_bills first to discover ids', explains when to pass include_transactions along with account_id, and states that transactions can be fetched via openfinance_list_transactions with a from/to range ending at billClosingDate. It also clarifies when transactions_basis is exact versus estimate, and warns against summing transactions to rebuild totalAmount.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most openfinance_* tools target a distinct resource and action, and the descriptions carefully separate overlapping endpoints like openfinance_list_transactions vs openfinance_list_transactions_by_item and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills. The main ambiguity risk is the broad marketplace mega-tool, but its many sub-capabilities are explicitly enumerated.

Naming Consistency4/5

Tool names consistently use snake_case with a strong openfinance_ prefix and verb-led patterns like list_, get_, update_, disconnect_, and force_sync. Minor deviations exist: openfinance_provider_status lacks a verb, openfinance_get_accounts_detail is awkwardly pluralized, and the platform tools (connect, marketplace, authenticate) break from the prefix pattern.

Tool Count3/5

At 25 tools, the server sits at the heavy end of the appropriate range. The Open Finance domain is complex enough to justify most entries, but the inclusion of platform-level tools like marketplace, authenticate, connect, and toolkit_info makes the overall surface feel denser and less focused than a pure banking-data server.

Completeness4/5

The set provides strong coverage of the Open Finance lifecycle: connections, sync/status, accounts, balances, transactions, credit card bills, loans, investments, category management, and provider health. Minor gaps exist, such as no dedicated investment-detail-by-id tool and no way to set custom connection labels, but these are workable and do not create critical dead ends.