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

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

There are rich behavioral disclosures beyond the annotations' readOnlyHint/idempotentHint/destructiveHint: transactions_basis distinctions with confidence levels, authoritative totalAmount warning against summing, the meaning of payments[] relative to the current bill, the absence of a paid/status field, and the cost/performance implication of include_transactions. This goes far beyond the metadata.

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 every sentence carries essential operational knowledge: what is returned, what the opt-in does, basis precision, payment semantics, and recommended alternatives. It is tightly organized and front-loads the core purpose before diving into complications, with no filler or repetition.

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?

For a complex tool with no output schema, the description is exceptionally complete. It covers the batch shape, field semantics, edge cases like open vs closed bills, estimate windows, the transactions_hint, manual retrieval workflow, and limitations of payments[] data. An agent can confidently invoke it correctly with this description alone.

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 shoulders the burden. It explains bill_ids (array, discover via list), include_transactions, account_id (required when opt-in), and role of billClosingDate. However, transactions_detail (compact/rich/raw) is entirely unmentioned, and the description does not clarify what each enum value changes in output shape.

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 precise verb and resource: "Returns bill-level detail for one or more credit card bills by id (GET /bills/:id)" and enumerates the exact fields returned. It clearly distinguishes itself from sibling tools by explaining that bill ids come from openfinance_list_credit_card_bills and that transactions may instead be fetched with openfinance_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?

The description provides explicit when-to-use guidance: discover ids via openfinance_list_credit_card_bills first, pass bill_ids as an array, and choose the opt-in include_transactions path only when full transaction scan is justified. It also explicitly directs users to openfinance_list_credit_card_bills for paid status and to openfinance_list_transactions for manual transaction retrieval, with the range ending at billClosingDate.

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.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose: accounts, transactions, credit card bills, loans, investments, connections, sync, categories, provider status, and platform meta-tools are all separable. Even the two transaction tools differ (per-account list vs consolidated analysis) and the two status tools differ (connection vs provider health).

Naming Consistency4/5

The openfinance_* prefix is consistently applied across the financial domain, and most follow a verb_noun pattern (list_accounts, get_balance, update_category). However, there are non-prefixed tools (authenticate, connect, marketplace, toolkit_info) and one outlier like openfinance_provider_status (noun instead of verb) that slightly break the pattern.

Tool Count3/5

25 tools is at the upper boundary of what feels heavy for a single server, even for a comprehensive financial aggregation toolkit. The number is justified by the breadth of domains covered (accounts, credit, loans, investments, connections, platform features), but it requires careful agent selection and might be better split into separate servers.

Completeness5/5

The surface covers the full financial data lifecycle: listing and fetching details for all asset types, updating transaction categories, managing connections (list, sync, disconnect, reauth), checking provider health, and searching connectors. There are no obvious dead ends—every domain has read and appropriate write/update operations.