Skip to main content
Glama

Dock MCP

by io.github.mcp-dir

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?

The description goes far beyond the readOnlyHint annotation by explaining that transactions are not included by default, that transactions_basis may only yield estimates, that totalAmount should be trusted over a manually summed transaction total, and that payments[] describes the prior bill—not the current bill. The content is consistent with the annotations.

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 dense, with clear topic sections and no dead sentences. The return fields come first, then the conditional transaction opt-in, then the matching semantics and billing caveat. The formatting makes the dense information navigable.

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 tool with no output schema, the description does a full open job: it covers the fields, batch shape, transaction shifting, status limitations, and the actual billing-cycle meaning of payments[]. An agent has enough information to choose workflows correctly and to interpret results safely.

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 carries the burden of explaining most parameters: bill_ids is to be used as an array, include_transactions is the opt-in trigger, and account_id is needed because bills lack an account reference. The one gap is transactions_detail and its compact/rich/raw enum, which is never explained.

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 begins with a specific verb and resource: 'Returns bill-level detail for one or more credit card bills by id,' and enumerates the returned fields. It clearly distinguishes itself from the sibling listing tool by focusing on detail retrieval by id.

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 to use openfinance_list_credit_card_bills first to discover bill ids, and to prefer that sibling for the paid/status field. It also routes transaction-level needs to openfinance_list_transactions, giving both usage context and exclusion timing.

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

All Dock 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/5.0
Disambiguation4/5

Most openfinance_ tools target distinct resources (accounts, transactions, bills, loans, investments, connections, categories), so the core surface is clearly separated. However, several pairs could be confused at first glance: list_transactions vs list_transactions_by_item (both return transactions but at different scopes), get_credit_card_bill vs list_credit_card_bills (bill detail vs list of bills), and get_account_balance vs get_accounts_detail (balance snapshot vs full account object). The detailed descriptions help, but the overlap is nontrivial.

Naming Consistency4/5

The openfinance_* tools follow a consistent pattern (list_, get_, update_, search_, force_sync, provider_status, disconnect_bank), all using snake_case with a clear domain prefix. However, the general platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) have no such prefix or consistent verb_noun pattern, mixing the convention. The finance subset is strong, but the overall set isn't uniform.

Tool Count3/5

At 25 tools, this is at the upper boundary of acceptable for a broad financial domain covering connections, accounts, transactions, credit cards, loans, investments, categories, and provider health. Each tool adds real capability, so it doesn't feel bloated, but it's heavier than typical and pushes the borderline between well-scoped and too many.

Completeness4/5

The surface covers the Open Finance lifecycle thoroughly: connection management (list, reconnect, force sync, disconnect, provider status), account/balance reads, transaction listing (with filters, pagination, rich detail), credit card bills (closed and open/debt), loans, investments, category management, and a connector search. Obvious gaps like a tool for creating connections are handled via widget URLs rather than an API call, so the coverage feels adequate. Minor gaps exist (e.g., no explicit tool for updating a connection's credentials beyond reconnect URLs), but nothing that would block core workflows.

Resources