Skip to main content
Glama

Sicoob 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. 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"
+}
  10. Added
  11. Removed
  12. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already state readOnlyHint=true/idempotentHint=true/destructive=false, and the description adds meaningful behavior beyond them: transactions_basis can be bill_id/date_window/unavailable or unavailable, with a Confidence flag; include_transactions costs another full transaction scan; totalAmount is authoritative and must not be recomputed; the bank payload lacks a paid/status field; and payments[] typically reflect the previous bill. Nothing contradicts 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?

Although lengthy, the description is structured in clear logical blocks: core return shape, optional transaction payload, payment-status caveat, and batch response shape. Every sentence carries warning or operational guidance; there is no filler. The highest-stakes warnings began: totalAmount authoritative, bill_ids discovery, and paid-status caveat.

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?

With no output schema, the description usefully documents the response shape, { results, errors }, key fields, and branch behavior for include_transactions. transaction_detail remains the one notable communication, and the exact value semantics of transactions_detail are not clarified. Otherwise, for a read-only credit-card-bill detail tool, the description is thoroughly context-rich.

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 must compensate. It does compensate well for bill_ids ('pass as array; use list_bills first'), account_id ('needed because the bill carries no account reference'), and include_transactions (defines the opt-in behavior exactly). However, the transactions_detail parameter is never mentioned or defined, leaving the compact/rich/raw distinction to be inferred only from the enum names.

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?

Opens with a concrete verb+resource pair: 'Returns bill-level detail for one or more credit card bills by id (GET /bills/:id)' and enumerates the returned fields. It also distinguishes itself from sibling tools by pointing to openfinance_list_credit_card_bills for discovering ids and to openfinance_list_transactions as the standalone transaction alternative, so an agent can reliably tell it apart.

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: pass include_transactions:true plus account_id to include transactions; otherwise rely on totalAmount; use list_credit_card_bills to discover ids; call list_transactions directly for transactions; and prefer list_credit_card_bills for payment status. It also warns against assuming a bill was paid based on payments[] being non-empty. This goes well beyond a bare capability statement.

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

All Sicoob 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

A3.7/5.0
Disambiguation4/5

Most openfinance_* tools target clearly distinct resources (accounts, transactions, bills, loans, investments, connections, categories). Minor overlap exists—list_accounts returns balances and list_transactions_by_item consolidates what list_transactions provides—but the detailed descriptions distinguish them adequately.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (get_*, list_*, update_*, force_sync, search_*) with one slight deviation: openfinance_provider_status omits a verb. The non-openfinance platform tools (authenticate, connect, marketplace, report_bug, etc.) break the prefix pattern, creating two naming conventions within the same server.

Tool Count3/5

25 tools sits at the upper boundary of acceptable for a comprehensive Open Finance banking adapter, covering accounts, transactions, credit cards, loans, investments, and connection management. However, including meta-platform tools like marketplace and toolkit_info inflates the count and makes the set feel heavier than a pure banking tool surface.

Completeness4/5

The tool surface covers the core Open Finance lifecycle well: list/get accounts, balances, transactions, credit card bills, loans, investments, connection management, category correction, and provider status. Gaps include no direct new-bank connection tool (only URLs) and no investment detail endpoint beyond transactions, but agents can work around these.

Resources