Skip to main content
Glama

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=true and idempotentHint=true, and the description adds substantial behavior beyond that: the bill payload lacks transactions (they live on the account), the transactions_basis can be exact vs estimate with confidence:'low', the totalAmount is authoritative and must not be reconstructed by summing transactions, and the payments[] semantic warning. The description does not contradict any annotation.

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?

Dense but earned: every sentence of this long description carries value — batch shape, field semantics, bill-closing boundaries, basis semantics, paid-status caveat, opt-in cost. Front-loaded with the main purpose, organized via explicit markers (OPT-IN, NOTE). The lack of subheadings and heavy inline parentheses make it less scannable than it could be, but this is a small cost for the complexity of the domain.

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?

For a tool with no output schema, 4 parameters, and high domain complexity, the description is very complete: return fields, batch result shape, transaction matching semantics, cost trade-off, and routing to sibling tools are all covered. The remaining gap is the undocumented transactions_detail parameter, which is significant enough to drop this from 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?

Schema description coverage is 0%, so the description must compensate. It does for three of the four parameters: bill_ids (array usage and discovery path), include_transactions (cost, required account_id, resulting fields), and account_id (why it is needed). Missing entirely is the transactions_detail parameter (compact/rich/raw enum) — it is never mentioned in the description.

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 precise verb-resource-scope statement: 'Returns bill-level detail for one or more credit card bills by id', including the exact HTTP mapping GET /bills/:id. It distinguishes itself from sibling tools by naming the such boundaries: list bills vs get bill detail vs list transactions.

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?

Explicit when-to-use and workflow guidance: use openfinance_list_credit_card_bills first to discover bill_ids, use openfinance_get_credit_card_bill for detail, and use openfinance_list_transactions with the account_id and a from/to range ending at billClosingDate to fetch transactions manually. It also explicitly says to check payment_status via openfinance_list_credit_card_bills rather than assuming payments[] means the bill was paid.

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

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., force_sync vs get_item_status, list_accounts vs get_accounts_detail). Minor overlap exists between list_transactions and list_transactions_by_item, and between get_account_balance and list_accounts (which also contains balance), but descriptions clarify when each should be used.

Naming Consistency4/5

All openfinance_* tools follow a consistent snake_case verb_noun pattern (list, get, force_sync, disconnect, update). The generic tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are also lowercase with underscores where needed, though they lack the openfinance prefix. No mixing of camelCase or chaotic patterns, so mostly consistent with minor deviation.

Tool Count3/5

25 tools is on the heavy side for a single server, but justified given the breadth of Open Finance operations (accounts, transactions, bills, loans, investments, connections, categories, provider status). The count is borderline heavy but not excessive for the domain, though some consolidation could be possible (e.g., merging get_account_balance into list_accounts).

Completeness5/5

The tool surface covers the full lifecycle for financial data: listing, getting details, forcing syncs, disconnecting, updating categories, checking provider status, and handling investments/loans/bills. No obvious dead ends; even connection management includes search, connect URLs, and re-authentication flows. The set appears comprehensive for its intended purpose.