Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Resolve merchant identity

payment-intelligence_merchant-identity-resolve

Match transaction merchants against a caller-supplied directory. Unmatched names keep the supplied transaction text. Price $0.04 USDC. POST /api/v1/payment-intelligence/merchant-identity-resolve. 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_merchant-identity-resolve"
  }
}

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 does carry useful burden: it discloses pricing ($0.04 USDC), the payment gate (402 and no execution when unpaid), the HTTP method/path, and the unmatched-name fallback. It omits whether the operation mutates anything, whether results are persisted or returned only, and what the response contains — significant for a paid, zero-annotation 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 with the core behavior front-loaded, then the fallback, price, and transport details. The endpoint path and price are operational rather than filler, though the raw POST path adds little for an agent that never calls the HTTP layer directly.

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 tool with nine optional parameters, deeply nested objects, no annotations, and no output schema, the description is thin. An agent knows what the tool conceptually does but not how to shape a valid request or what it gets back, which is a substantial gap at this complexity level.

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 merchants, accounts, transactions, and corrections objects, and the description explains none of them. 'Caller-supplied directory' and 'supplied transaction text' loosely hint at the merchants/transactions and text/csv/json inputs, but the schema does the rest of the work 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?

States a specific verb and resource: matching transaction merchants against a caller-supplied directory, plus the fallback for unmatched names. It does not explicitly distinguish itself from the nearby transaction-categorization-correct sibling, which also touches merchant/category text, leaving a small ambiguity.

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 guidance: nothing says when to resolve identities versus categorizing or correcting transactions, and no guidance on which of the four input channels (text, csv, json, file) to choose. The only usage-adjacent information is the fallback behavior for unmatched names.

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