Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Calculate affordability data

payment-intelligence_affordability-data-calculate

Calculate inflow, outflow, subscription estimates, and income ratios from supplied transactions. No affordability decision is returned. Price $0.05 USDC. POST /api/v1/payment-intelligence/affordability-data-calculate. 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_affordability-data-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
accountsNo
merchantsNo
correctionsNo
transactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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, and it does disclose valuable operational traits: a $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. That is real context an agent needs. However, it says nothing about the return payload, which of the four input formats is expected, or what happens when no input source is supplied (required parameters = 0).

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?

Four short sentences, purpose first, then scope, then pricing and failure behavior. No filler. The endpoint path is arguably boilerplate an agent cannot act on, but it is brief and does not crowd out the substance.

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?

This is a high-complexity tool: 9 parameters, deeply nested objects, zero schema descriptions, no annotations, and no output schema. The description covers purpose, cost, and payment failure but leaves the entire input contract and return shape unexplained, which is not enough for an agent to call it correctly.

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 transaction, account, merchant, and correction objects, and the description only gestures at 'supplied transactions.' It never explains the mutually exclusive csv/json/text/file input paths, the meaning of asOf for ratio computation, or the role of corrections and merchant aliases. With low coverage and high parameter count, the description fails to compensate.

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?

The description names a specific verb (calculate) and enumerates the concrete outputs: inflow, outflow, subscription estimates, and income ratios from supplied transactions. The explicit scoping statement 'No affordability decision is returned' prevents confusion with decisioning tools. It does not, however, differentiate itself from siblings like subscription-spend-identify or income-stability-analyze, which compute overlapping-sounding metrics.

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?

'from supplied transactions' plus 'No affordability decision is returned' implies the intended use: compute derived metrics rather than produce a lending verdict. No alternatives are named, no when-not-to-use conditions are given, and nothing tells the agent how this differs from the subscription or income-stability siblings.

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