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.6/5.0
Behavior5/5

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

The annotations already indicate read-only and idempotent behavior, but the description goes much further by disclosing that no paid/status field exists, that payments[] refer to the prior cycle, and that transactions_basis may be exact or estimated. It also warns that totalAmount is authoritative and should not be recomputed from transactions, which is essential for correct use and differentiates this tool well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but each sentence adds a distinct operational fact. It is front-loaded with the core behavior and key output fields, then layers caveats and admonitions only where needed. There is no filler or redundant repetition of the schema.

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, the description is unusually complete about response shape, edge cases, estimate semantics, and parameter interactions. The only notable gap is the undocumented transactions_detail parameter and its compact/rich/raw differences. Overall, a capable agent could safely call this tool despite missing that one detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% descriptions, so the description carries the burden of explaining parameters. It explains bill_ids, account_id, and include_transactions with meaningful behavioral context. However, the transactions_detail enum (compact, rich, raw) is never mentioned or explained, leaving a material parameter undocumented.

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 'Returns bill-level detail for one or more credit card bills by id', naming the specific verb, resource, and HTTP endpoint. It lists concrete response fields such as dueDate, billClosingDate, totalAmount, and payments[], and clearly positions itself relative to sibling tools by instructing bill discovery via openfinance_list_credit_card_bills.

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 gives explicit routing: 'use openfinance_list_credit_card_bills first to discover ids', 'prefer openfinance_list_credit_card_bills' for paid status, and openfinance_list_transactions for fetching transactions manually. It also explains when include_transactions is useful and when the transactions basis is an estimate, so the agent knows exactly when this tool is the right choice.

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.8/5.0
Disambiguation3/5

The openfinance_* tools are mostly distinct, but several have overlapping boundaries: openfinance_list_transactions vs openfinance_list_transactions_by_item, openfinance_get_item_status vs openfinance_provider_status, and openfinance_list_accounts carrying balance vs openfinance_get_account_balance. The platform-level tools also blur somewhat: marketplace, toolkit_info, and connect all touch installed or available services.

Naming Consistency3/5

The openfinance_* group follows a consistent list/get/update verb pattern in snake_case, but platform-level tools like authenticate, connect, marketplace, report_bug, show_version, and toolkit_info break that convention. The set is readable, but it is split between two clearly different naming styles.

Tool Count3/5

At 25 tools, the server is at the heavy end, and several are platform/MCP-management helpers rather than core banking capabilities. The count is not absurd for a broad Open Finance + marketplace adapter, but it feels more cluttered than a focused financial data toolset should be.

Completeness4/5

The Open Finance surface is thorough: accounts, transactions, balances, credit card bills, loans, investments, connection lifecycle, sync, provider status, and category correction are all covered. The main gaps are the absence of a direct connect/create action (only URLs are returned) and no write operations beyond category updates, but for a read-centric financial data adapter this is close to complete.