Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Detect recurring payments

payment-intelligence_recurring-detect

Detect repeating merchant and amount patterns from supplied transaction dates. Cadence is labeled from spacing only. Price $0.05 USDC. POST /api/v1/payment-intelligence/recurring-detect. 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_recurring-detect"
  }
}

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 supplied, the description carries the full burden, and it does disclose non-obvious operational facts: a $0.05 USDC cost, the POST endpoint, and that unpaid calls return 402 without executing. Those details materially affect whether an agent should call it and how to handle failures. It is silent on permissions, rate limits, and what the response contains, so it is partial rather than complete.

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, each carrying distinct information: purpose and caveat first, then price, endpoint, and payment failure behavior. No filler or repetition. The commercial and transport details are appended efficiently rather than buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter analytical tool with no annotations and no output schema, the description should say more about how to supply the transaction data and what comes back. Pricing and 402 behavior are well covered, and the cadence caveat sets expectations, but input handling and result shape are unaddressed. It is adequate to attempt a call yet thin for a tool of this complexity.

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, and the description names no parameter and gives no format or semantics for csv, json, text, file, asOf, transactions, merchants, accounts, or corrections. The phrase 'supplied transaction dates' hints that transactions input is required, but the mutual exclusivity and shape of the several input channels is left entirely unexplained. This is a substantial gap that the description does not compensate for.

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?

Specific verb 'Detect' plus a concrete resource: repeating merchant and amount patterns derived from supplied transaction dates. It also scopes the output ('Cadence is labeled from spacing only'), which tells an agent what kind of answer to expect. It stops short of differentiating itself from the nearby subscription-spend-identify sibling.

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?

The description never states when to reach for this tool versus alternatives such as subscription-spend-identify or transaction-categorization-correct. The clause 'Cadence is labeled from spacing only' is a useful caveat about output quality but is not usage guidance. An agent must infer the appropriate moment to call it.

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