Fibalo

Bank: Bank Transactions Summary

bank_transactions_summary

Read-onlyIdempotent

Money in and out for a period, grouped: "who did we pay in July, how much".

Every group carries credit_cents, debit_cents and net_cents in its own currency; totals are listed per currency for the same reason.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "bank_transactions_summary"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	matches counterparty name, IBAN, or the remittance text.
`company`	Yes	company name or id.
`to_date`	No	YYYY-MM-DD, last booking date to include.
`group_by`	No	counterparty, month, direction or account.	counterparty
`direction`	No	restrict to credit or debit before grouping.
`from_date`	No	YYYY-MM-DD, first booking date to include.
`account_id`	No	restrict to one bank account.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful output semantics beyond annotations: each group carries credit_cents, debit_cents, and net_cents in its own currency, and totals are listed per currency.

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?

Front-loads the core purpose in the first sentence, and the second sentence adds materially useful output-currency context. There is no wasted text and the example is concise.

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?

Given rich annotations, full schema coverage, and an output schema, the description is largely complete for a read-only summary tool. The remaining gap is explicit differentiation from list_bank_transactions for ungrouped transaction retrieval.

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

Parameters3/5

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

Schema description coverage is 100%, so all seven parameters are documented in the schema. The description adds only the general grouping/period concept and does not provide additional parameter syntax or format guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific aggregation resource and operation: money in/out over a period, grouped, with an example clarifying the summary intent. It distinguishes itself from raw listing tools by emphasizing grouping, but does not explicitly name list_bank_transactions as the alternative.

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

Usage Guidelines3/5

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

The example "who did we pay in July, how much" implies when grouped summary totals are wanted, but there is no explicit when-to-use or when-not-to-use guidance. It also does not name sibling tools or explain when a raw transaction list is preferable.

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

All Fibalo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?