Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Correct transaction categorization

payment-intelligence_transaction-categorization-correct

Apply caller-supplied category corrections to matching transaction ids or merchants without inventing categories. Price $0.04 USDC. POST /api/v1/payment-intelligence/transaction-categorization-correct. 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_transaction-categorization-correct"
  }
}

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/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 contribute real operational context: a $0.04 USDC price, a 402 response for unpaid calls, and the guarantee that unpaid calls do not execute. It does not say whether corrections are persisted or only reflected in the response, nor anything about idempotency or failure handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the behavioral constraint first, followed by price and endpoint mechanics. Every sentence adds information and nothing is redundant.

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 complex nine-parameter tool with nested objects and no output schema, but the description only covers purpose and payment mechanics. It omits how the alternate input formats work, what the response contains, and whether corrections mutate stored data, which is significant for a write-flavored operation.

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, so the description must compensate. It gestures at the core inputs, corrections, transaction ids, and merchants, but says nothing about the csv, json, text, file, asOf, or accounts inputs, leaving most of the payload shape undocumented.

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 states a specific verb and target: applying caller-supplied category corrections to matching transaction ids or merchants, with the explicit constraint that it will not invent categories. That distinguishes it functionally from an inference/classification tool, though it does not name the sibling classifier it contrasts with.

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 use this versus the classify or merchant-identity siblings. The phrase 'without inventing categories' only implicitly hints that the caller must already know the target category, leaving the agent to infer the selection condition.

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