Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Analyze income stability

payment-intelligence_income-stability-analyze

Summarize labeled income credits by month and report variability from supplied amounts only. Income is never invented. Price $0.05 USDC. POST /api/v1/payment-intelligence/income-stability-analyze. 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_income-stability-analyze"
  }
}

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
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: deterministic computation from supplied amounts only, no invented income, a $0.05 USDC price, and that unpaid calls return 402 without executing. That billing and failure-path detail is valuable. It omits authentication requirements and does not describe the shape of the result, though.

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 short and front-loads the core function before moving to pricing and endpoint mechanics. Every sentence is functional, though the endpoint path and price could be consolidated into one billing clause rather than occupying two sentences.

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 nine-parameter tool with nested objects, zero annotation coverage, zero schema descriptions, and no output schema. Against that complexity, the description says nothing about which input form to supply, how transactions are identified as income, or what the returned variability report contains. It is adequate on billing but insufficient for correct invocation.

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 nine parameters, including nested transactions, accounts, merchants, corrections, and four alternate payload channels (csv, json, text, file). The description mentions 'labeled income credits' and 'supplied amounts' but never explains which input channel to use, what counts as labeled, or what asOf means. The agent must reverse-engineer all of this from an undocumented 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?

The description gives a specific verb and resource: summarize labeled income credits by month and report variability. That is far more informative than the title alone. It stops short of distinguishing this analysis from siblings such as recurring-detect or account-cashflow-compare, so an agent must infer the boundary.

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?

There is no explicit statement of when to choose this tool over the cashflow-comparison or recurring-detection siblings, and no prerequisites are given. The constraint that only supplied, labeled amounts are used implies the input must be pre-labeled income data, but the agent has to infer that. No exclusions or alternative routing are provided.

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