Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Analyze payment failure patterns

payment-intelligence_failure-pattern-analyze

Find failed, declined, or returned payment wording and statuses in supplied transactions and group counts by merchant text. Price $0.04 USDC. POST /api/v1/payment-intelligence/failure-pattern-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_failure-pattern-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

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 does deliver genuinely useful operational context: price ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 and do not run. It does not explain what qualifies as a 'failure pattern', how grouping handles non-merchant rows, or whether results are deterministic — meaningful gaps for a paid analysis tool.

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 tight sentences, front-loaded with the core operation before the commercial and transport details. The API path is mildly redundant for an MCP caller but is short and not disruptive.

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, nested-input, no-output-schema, no-annotation tool, the description is far too thin — the payer-model behavior is covered but input selection, failure definition, and result shape are not. An agent could not confidently construct a correct call from this text.

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?

Nine parameters with 0% schema description coverage and nested objects. The description alludes only to 'transactions' and merchant text grouping; it says nothing about csv/json/text/file alternates, accounts, corrections, or asOf, all of which an agent must guess at from field names.

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: find failed/declined/returned payment wording and statuses in supplied transactions, then group counts by merchant text. That is a distinctive operation an agent could distinguish from siblings like transaction-categorization-correct or merchant-identity-resolve, though no sibling is named explicitly.

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?

Usage is only implied by 'in supplied transactions' — there is no statement of when this analysis is appropriate versus the sibling analyzers, no prerequisites for input shape, and no exclusions. The agent must infer the scenario from the name alone.

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