Skip to main content
Glama

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

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true. The description adds substantial behavioral details beyond annotations: it explains the consolidation logic, truncation at 5000/account with a flag, provider incident block, and the effect of different granularity/detail options. No contradiction with annotations.

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 long but well-structured, starting with the core purpose, then detailing options and special cases. Every sentence adds value, though it could be slightly more concise. The length is justified by the tool's 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 the absence of an output schema, the description compensates by describing the output structure (compact summary with fields like entradas/saídas, por_mes, top despesas, by_account) and special cases (truncation, provider incident). It fully covers the tool's behavior and usage.

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?

Schema description coverage is 0%, so the description carries the full burden of explaining parameters. It explains all major parameters (item, from, to, granularity, detail, type, item_ids) with their values, defaults, and behavior. The top_n parameter is implied but not explicitly named, yet the overall coverage is thorough and highly informative.

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 that the tool performs consolidated cash-flow analysis for a bank connection in one call, resolving accounts internally. It explicitly distinguishes itself from sibling tools by noting that it eliminates the need to call openfinance_list_accounts first.

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?

The description provides clear context on when to use the tool (e.g., for 'fluxo de caixa', 'maiores gastos') and explains the options for granularity and detail. It does not explicitly state when not to use it, but the context from sibling tools and the detailed usage scenarios compensate.

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