Skip to main content
Glama

Bradescard MCP

by io.github.mcp-dir

openfinance_list_transactions_by_item

Read-onlyIdempotent

Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call. Resolves the connection's accounts internally and fans out their transactions, so you do NOT need to call openfinance_list_accounts first nor carry account_id uuids between calls. Pass item (connector_id, connector_name or item_id) to target one bank, or OMIT it to analyze ALL linked banks at once. from/to are ISO dates (YYYY-MM-DD). Default granularity:'monthly' returns a COMPACT summary (no raw rows): total entradas, saídas, saldo_liquido, monthly evolution (por_mes), and top_despesas/top_recebimentos (largest N each), plus a per-account breakdown (by_account). Use this for 'análise anual/mensal', 'fluxo de caixa', 'entradas e saídas', 'maiores gastos/recebimentos'. Set granularity:'raw' to ALSO get every consolidated transaction (heavier — only when itemized rows are needed); combine with detail:'rich' to enrich those rows with merchantInfo (cnpj/cnae/businessName/category) + extra creditCardMetadata (billId, purchaseDate, fees), or detail:'raw' for the full untouched Pluggy object per row, when the connector provides them. type filters BANK or CREDIT accounts. On a connection with many transactions the scan caps at 5000/account and flags truncated:true. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a connected bank: the totals/rows may be incomplete or wrong until the provider recovers, and reconnecting does not fix it.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
itemNo
typeNo
top_nNo
detailNo
item_idNo
item_idsNo
granularityNo

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. Changed2 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / item_ids
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  12. Added
  13. Removed
  14. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds critical details: 5000-transaction cap per account with truncation flag, provider incident block affecting data completeness, internal account resolution and fan-out, and behavior of granularity/detail options. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is lengthy but efficient: starts with core value proposition, then parameter details, then caveats. Some repetition (e.g., mentioning item parameter twice) could be trimmed. Overall well-structured for the complexity.

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?

Given 9 parameters, no required fields, no output schema, the description covers all necessary aspects: parameter semantics, return structure (summary vs raw rows), limitations (cap, provider incidents), and intended use cases. Completely sufficient for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, description fully compensates by explaining each parameter's purpose, formats (ISO dates, enums), defaults (granularity='monthly'), and what each granularity/detail combination returns. Also clarifies item parameter accepts multiple identifier types and bulk support via item_ids.

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?

Description clearly states it performs consolidated cash-flow analysis for a whole bank connection, resolving accounts internally. It distinguishes itself from similar tools like openfinance_list_accounts and openfinance_list_transactions by eliminating the need for separate calls and providing aggregated data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (e.g., monthly/annual analysis, cash flow, top expenses/revenues) and how to target one bank or all banks. Mentions bulk support. Does not explicitly contrast with sibling openfinance_list_transactions, but the context implies this is the comprehensive version.

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

All Bradescard 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.2/5.0
Disambiguation4/5

Most tools are highly distinct, targeting different resources (accounts, transactions, bills, loans, investments, connections). However, openfinance_list_transactions and openfinance_list_transactions_by_item both return transaction data with different scopes, which could cause misselection. Also openfinance_get_item_status vs openfinance_provider_status are distinct but similar in name.

Naming Consistency5/5

The openfinance_* tools follow a consistent verb_noun pattern (list_accounts, get_credit_card_bill, force_sync). Generic tools (authenticate, connect, marketplace) are also clearly named and consistent within their own domain. No mixed conventions or chaotic naming.

Tool Count4/5

At 25 tools, the server is on the heavier side (borderline of the 16-25 range) but each tool serves a clear purpose in the open finance domain, covering multiple resource types and auxiliary functions like marketplace and status. A slight trim could be made (e.g., merging some list/get pairs), but it's not excessive.

Completeness4/5

The server covers the full read lifecycle for accounts, transactions, bills, loans, and investments, plus connection management (list, disconnect, force sync) and category updates. Minor gaps like lack of direct deletion for financial records are acceptable since those are not typical operations. The generic tools (marketplace, auth, version) round out the toolkit.

Resources