Skip to main content
Glama

Midway 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

Schema Changelog

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

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. 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"
+}
  18. Added
  19. Removed
  20. First observed

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 annotations' readOnly/idempotent/destructive hints. It reveals that the bill payload has no embedded transactions, that transactions_basis may be a low-confidence estimate, that pending bills have no billId, that payments[] reflect the previous bill's payment, and that totalAmount is authoritative — none of this is inferable from the schema.

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 never wasteful: it uses clear sectioning and front-loads the core return fields before caveats. Every paragraph covers a distinct operational concern, and no sentence merely restates the tool name or schema field names.

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?

Despite lacking an output schema, the description covers the response shape, batch errors, transaction-matching caveats, optional performance cost, authoritative total semantics, and paid-status pitfalls. An agent has the information needed to use this tool correctly and know what the results mean.

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 must carry parameter meaning, and it does well for bill_ids, account_id, and include_transactions. However, it never explains transactions_detail or its enum values (compact/rich/raw), leaving a real gap for an agent deciding which detail level to request.

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 states an explicit action and resource: 'Returns bill-level detail for one or more credit card bills by id (GET /bills/:id)'. It also distinguishes itself from bill listing and transaction listing tools by defining its exact output scope, including the optional transaction expansion.

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?

It gives explicit routing guidance: use openfinance_list_credit_card_bills first to discover IDs, prefer that list tool for paid status, and optionally use openfinance_list_transactions for transaction retrieval. It also clarifies when to pass include_transactions and why the opt-in may be worth the extra cost.

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

All Midway 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
Disambiguation3/5

The openfinance_* family is largely well-differentiated by resource and action, but the monolithic `marketplace` tool bundles search, invoke, install, billing, and prompt-library actions into one name, creating ambiguity about where platform capabilities live. Additionally, `openfinance_list_transactions` and `openfinance_list_transactions_by_item` both return transaction data and could be misselected despite their different aggregation intent.

Naming Consistency3/5

The openfinance_* tools consistently follow a clear verb_noun pattern, which gives the majority of the surface a predictable shape. But the generic platform tools mix bare verbs (`authenticate`, `connect`), nouns (`marketplace`, `toolkit_info`), and verb_noun names (`report_bug`, `show_version`), so the server has two naming dialects rather than one uniform convention.

Tool Count3/5

At 25 tools, this sits right at the top of the heavy range, and the server genuinely spans two broad domains: MCP platform administration and Open Finance banking data. The count is defensible given the breadth, but it is not a lean or easily navigable surface for an agent.

Completeness4/5

The Open Finance side is quite complete, covering connections, accounts, transactions, credit card bills, loans, investments, categories, provider status, sync, and disconnection. The platform side covers authentication, connection status, marketplace operations, bug reporting, and versioning, though some marketplace sub-actions are packed into one tool and bank connection itself is only reachable through URLs returned by other tools.

Resources