Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Audit financial data quality

payment-intelligence_financial-data-quality-audit

Combine classification, recurring spend, merchants, income, failures, corrections, cashflow, and missing-field checks from supplied records. Price $0.12 USDC. POST /api/v1/payment-intelligence/financial-data-quality-audit. 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_financial-data-quality-audit"
  }
}

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, and it does add real value by disclosing price ($0.12 USDC) and the 402 failure mode where the call does not run. However, it says nothing about the read-only nature of the operation, what the audit returns, or what happens when zero records are supplied (all 9 parameters are optional), leaving significant behavioral gaps.

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 capability, followed by price and endpoint. The POST path partly duplicates the tool name but is compact; there is little wasted wording overall.

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?

For a 9-parameter tool with nested objects, no output schema, and no annotations, the description is thin: it omits return shape, input-format selection, and behavior when optional arrays are empty. The pricing and 402 note are helpful but do not compensate for those gaps.

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% and the description does not map to any parameter. It never explains the four alternative input channels (csv, json, text, file), the purpose of asOf, or the roles of accounts, merchants, corrections, and transactions, so an agent gets no help choosing among 9 undocumented inputs.

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 action (combining a named set of checks: classification, recurring spend, merchants, income, failures, corrections, cashflow, missing-field) over supplied records, which is more informative than a generic 'audit' label. It does not explicitly distinguish itself from the individual sibling tools that appear to perform each of those checks separately, so an agent must infer that this is the bundled/composite option.

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 when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives (the per-analysis siblings). The only conditional statement is about unpaid calls returning 402, which is a payment precondition rather than usage guidance.

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