Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Classify open-banking transactions

payment-intelligence_open-banking-transaction-classify

Classify supplied transactions using description, merchant, category, and amount-sign hints. No bank connection is used. Price $0.04 USDC. POST /api/v1/payment-intelligence/open-banking-transaction-classify. 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_open-banking-transaction-classify"
  }
}

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.3/5.0
Behavior4/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 disclose the two non-obvious behaviors: a $0.04 USDC price and a hard failure mode where unpaid calls return 402 and do not execute. It also pins the transport (POST /api/v1/...). It does not cover idempotency, rate limits, or whether supplied categories are preserved versus overwritten, which are material for a classification 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?

Four short sentences, front-loaded with the purpose, followed by the two operational facts (no connection, price/402). Every sentence carries information, though the raw endpoint path is the least valuable line for an agent.

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 annotations, and no output schema, the description is thin: it never states what comes back (per-transaction labels? confidence? an array?), nor how the multiple input representations and corrections interact. The pricing disclosure is helpful but does not fill 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% across 9 parameters including nested objects, so the description must compensate and largely does not. It hints that merchant, category, description, and amount sign drive classification, but says nothing about the mutually plausible input modes (csv, json, text, file), nor what accounts, merchants, corrections, or asOf do.

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 ('Classify supplied transactions') and names the signal inputs used (description, merchant, category, amount-sign hints), so the operation is unambiguous. 'No bank connection is used' implicitly separates it from bank-connected siblings, but it never names a specific sibling such as transaction-categorization-correct, so differentiation is inferred rather than stated.

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?

'No bank connection is used' and 'supplied transactions' imply the precondition that the caller must already hold the data inline rather than link an account. However, there is no explicit when-to-use/when-not guidance and no pointer to the categorisation-correction or merchant-identity-resolve siblings, leaving the choice of tool to inference.

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