Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Compare account cashflow

payment-intelligence_account-cashflow-compare

Consolidate inflow and outflow by account and compare pairs only when currencies match. Price $0.05 USDC. POST /api/v1/payment-intelligence/account-cashflow-compare. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payment-intelligence_account-cashflow-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
accountsNo
merchantsNo
correctionsNo
transactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the price ($0.05 USDC), the POST endpoint, and that unpaid calls return 402 without executing. However, it says nothing about what a successful response contains, whether results are per-pair, or how the multiple input forms behave — significant gaps for a mutation-shaped paid endpoint.

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?

Three short sentences, front-loaded with the operation and constraint before pricing and endpoint details. Little waste, though the pricing/payment sentences consume space that could have documented input behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A complex tool with nine parameters, nested objects, no output schema, and no annotations should explain how the alternate payload inputs (csv, json, text, file, transactions) relate and what the comparison returns. The description covers billing mechanics but only one data rule, leaving an agent unable to call it correctly without guessing.

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

Parameters2/5

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

Schema description coverage is 0% across 9 parameters, including nested accounts, transactions, merchants, and corrections objects, so the description must compensate and largely fails. Only the currency-match rule vaguely points at the currency fields; nothing explains csv vs json vs text vs file vs transactions, asOf, or the correction/alias structures.

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 verb and resource: consolidating inflow/outflow by account and comparing account pairs, plus the currency-match constraint. It is meaningfully distinct from sibling tools like affordability-data-calculate, though it does not explicitly contrast itself with them.

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

Usage Guidelines2/5

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

No guidance on when to use this versus any sibling, no prerequisites beyond payment, and no exclusions. The only implied usage rule is that comparisons require matching currencies, which is a data constraint rather than a when-to-call rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources