Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Identify subscription spend

payment-intelligence_subscription-spend-identify

Identify subscription candidates from recurring cadence and subscription wording in supplied merchants or descriptions. Price $0.04 USDC. POST /api/v1/payment-intelligence/subscription-spend-identify. 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_subscription-spend-identify"
  }
}

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.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden and does disclose genuinely useful operational facts: a fixed price of $0.04 USDC, the POST endpoint, and that unpaid calls return HTTP 402 and do not execute. That payment-gate behavior is exactly the kind of context an agent cannot infer from the schema. It stops short of describing the success response, idempotency, or rate limits, so it is not a 5.

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?

The description is four short sentences with the core purpose front-loaded, followed by price, endpoint, and failure behavior. Every sentence carries information, though the endpoint path largely restates the tool name and could have been traded for input-mode detail.

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 tool: nine parameters, nested objects, zero schema description coverage, no annotations, and no output schema. Given that, the description should explain how the alternative input modes (csv, json, text, file) relate and what merchants/transactions contribute, but it does not. The payment and endpoint details are good, but the input contract an agent needs to call it correctly is missing.

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 file, transactions, merchants, accounts, and corrections objects, so the description must compensate and largely does not. It mentions only 'merchants or descriptions', leaving the csv/json/text/file input modes, the asOf parameter, and the transaction/account/correction structures unexplained in both the schema and the description.

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: it identifies subscription candidates using two stated signals (recurring cadence and subscription wording) in supplied merchant or description data. That is concrete enough for an agent to know what the tool returns conceptually, though it never contrasts itself with the sibling recurring-detect, which sounds closely related.

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 when-to-use or when-not-to-use guidance, and no mention of when an agent should prefer this over payment-intelligence_recurring-detect or merchant-identity-resolve. The only implicit signal is that the caller must already have merchant or description data to supply, which is a weak substitute for routing guidance.

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