Skip to main content
Glama

Necton 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

TDQS

A4.7/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains internal fan-out, truncation at 5000 per account with a flag, provider_incident block, and details on return format (compact vs raw). Annotations already indicate read-only, idempotent, non-destructive.

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 with the primary benefit. Every sentence adds value, but it is somewhat dense; minor trimming could improve readability without losing information.

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 complexity (9 parameters, no output schema, no param schema descriptions), the description is comprehensive: it covers purpose, parameter semantics, return values, limitations (truncation), and error conditions (provider_incident). It provides everything an agent needs to correctly invoke the tool.

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 fully compensates by explaining each parameter: 'item' (connector_id, connector_name, or item_id), 'from'/'to' as ISO dates, granularity defaults, detail options, type filtering, top_n, and bulk via item_ids. This adds meaning that the schema alone does not provide.

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 the tool's purpose: 'Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call.' It distinguishes from siblings by noting that it resolves accounts internally, avoiding 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 explicit use cases: 'Use this for 'análise anual/mensal', 'fluxo de caixa', 'entradas e saídas', 'maiores gastos/recebimentos'.' It also explains how to target one bank or all banks, but does not explicitly mention when not to use this tool or contrast with the sibling openfinance_list_transactions.

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

All Necton 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.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., force_sync vs get_item_status, list_accounts vs get_accounts_detail). Minor overlap exists between list_transactions and list_transactions_by_item, and between get_account_balance and list_accounts (which also contains balance), but descriptions clarify when each should be used.

Naming Consistency4/5

All openfinance_* tools follow a consistent snake_case verb_noun pattern (list, get, force_sync, disconnect, update). The generic tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are also lowercase with underscores where needed, though they lack the openfinance prefix. No mixing of camelCase or chaotic patterns, so mostly consistent with minor deviation.

Tool Count3/5

25 tools is on the heavy side for a single server, but justified given the breadth of Open Finance operations (accounts, transactions, bills, loans, investments, connections, categories, provider status). The count is borderline heavy but not excessive for the domain, though some consolidation could be possible (e.g., merging get_account_balance into list_accounts).

Completeness5/5

The tool surface covers the full lifecycle for financial data: listing, getting details, forcing syncs, disconnecting, updating categories, checking provider status, and handling investments/loans/bills. No obvious dead ends; even connection management includes search, connect URLs, and re-authentication flows. The set appears comprehensive for its intended purpose.

Resources