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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed3 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / include_transactions
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / transactions_detail
      Added value: +{
      +  "enum": [
      +    "compact",
      +    "rich",
      +    "raw"
      +  ],
      +  "type": "string"
      +}
  6. Added
  7. Removed
  8. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description is exceptionally transparent about behavior: no transactions in the bill payload, estimate basis versus exact bill_id, payments reflecting the previous bill, no paid/status field, performance cost of opt-in, and the authoritative totalAmount. It goes far beyond the simple readOnlyHint/idempotentHint annotations, and there is no contradiction.

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 significant operational information: field semantics, discovery sequence, transaction basis explanation, warnings, and alternatives. It is front-loaded with the basic return shape and then layers caveats logically, with no fluff.

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 and complex domain semantics, the description covers the essential return shape, batch shape, paid-status traps, bill-cycle boundary meaning, event horizon of discoverability, and manual fallback. This is complete enough for an agent to decide, call, and interpret the result confidently.

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 full burden of parameter meaning and does so well: bill_ids array, account_id required only for include_transactions, include_transactions behavior, and the returned metadata fields. The one gap is transactions_detail (compact/rich/raw), whose meaning is never explained and would likely confuse agents about the differences.

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?

States a specific verb and resource: 'Returns bill-level detail for one or more credit card bills by id (GET /bills/:id)'. It enumerates the specific fields returned and distinguishes itself from the sibling listing tool by saying to use openfinance_list_credit_card_bills first to discover ids and to check paid status.

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?

Gives explicit when-to-use guidance: the GET by id case, the sibling list tool for discovery and payment_status, and openfinance_list_transactions for fetching transactions manually. It also clearly explains the opt-in condition for including transactions and why it should be avoided unless needed.

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.