Skip to main content
Glama

BV 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. 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"
+}
  8. Added
  9. Removed
  10. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Adds significant behavioral context beyond annotations: caps at 5000 transactions per account with truncated flag, provider_incident block causing data incompleteness, and that raw granularity is heavier. Annotations already indicate read-only, idempotent, non-destructive, but description enriches with real-world constraints.

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?

The description is well-structured and front-loaded, but slightly long. However, each sentence adds value, covering purpose, usage, parameters, and caveats. Could be slightly more concise but is effective.

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 the tool's complexity (9 params, no output schema), the description is remarkably complete. It explains the consolidated output, the raw option, truncation, provider incidents, and bulk execution. No significant gaps.

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 description coverage, the description thoroughly explains all parameters: item, from/to dates, granularity, detail, type, top_n (implied), item_id/item_ids. It clarifies default behaviors and combined usage of granularity and detail.

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 clearly states it performs consolidated cash-flow analysis for a whole bank connection in one call, using specific verbs like 'list transactions' and 'analyze'. It distinguishes itself from sibling tools like openfinance_list_transactions by noting it resolves accounts internally without needing prior calls.

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?

Provides explicit guidance on when to use this tool: instead of calling openfinance_list_accounts first. Includes specific use-case queries and explains how to target one bank or all banks. Also mentions bulk support with item_ids.

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

All BV 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_* tools are mostly distinct resource/action pairs, but several boundaries blur: openfinance_list_transactions vs openfinance_list_transactions_by_item vs openfinance_get_credit_card_bill(include_transactions) all return transaction data, and openfinance_get_item_status / openfinance_provider_status / openfinance_list_connections all concern connection health. The monolithic marketplace tool also bundles search/describe/invoke/install/prompt-library operations, adding further ambiguity.

Naming Consistency4/5

The 19 openfinance_* tools follow a clean snake_case verb_noun pattern (list_accounts, get_item_status, update_transaction_category), but the six platform tools break it with bare verbs (authenticate, connect) and noun-style names (marketplace, toolkit_info). The split is namespace-based and still readable, so it is only a minor inconsistency.

Tool Count3/5

25 tools is on the heavy side, but the server spans two domains: an Open Finance banking surface (accounts, bills, loans, investments, connections) and a marketplace/platform layer (auth, search, prompts, bug reporting). Many openfinance tools are necessary for that breadth, though the count is high enough to feel bloated.

Completeness4/5

The Open Finance surface is nearly complete: connections can be searched, listed, disconnected, force-synced, and health-checked; accounts, transactions, bills, loans, and investments all have read/detail paths; transaction categories can be updated. Minor gaps exist, such as no granular marketplace tools outside the monolithic marketplace tool and no single-transaction detail endpoint, but core workflows do not dead-end.

Resources