Skip to main content
Glama

local_payment_methods

Read-only

List local bank-rail / wallet payment methods relevant to HelloBooks invoice collection (AR), B2B supplier payments (AP), and contractor payouts (UPI, RuPay, Razorpay, IMPS, NEFT, RTGS, BACS, FPS, CHAPS, Open Banking, Interac e-Transfer, EFT, PayID, PayTo, NPP, BPAY, ACH, Same Day ACH, Fedwire, RTP, Zelle, PayNow, FAST, GIRO, NZ Direct Credit, etc.). Returns rail (instant / same-day / next-day / multi-day), use-cases, issuing authority, HelloBooks support level, and operational notes (per-transaction caps, settlement windows, retirement timelines). Filter by country, useCase, rail, or id.

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": "local_payment_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoReturn a single payment method by id (e.g. "in-upi", "au-payid", "us-rtp").
railNoFilter by settlement rail (instant, same-day, next-day, multi-day).
countryNoFilter to one country (IN, US, CA, GB, AU, AE, SG, NZ).
useCaseNoFilter by payment use-case. Defaults to HelloBooks' invoice-collection + b2b-supplier + contractor-payout scope; pass an explicit value to widen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that, the description discloses the returned fields (rail, use-cases, issuing authority, support level, operational notes with caps, settlement windows, retirement timelines) and that useCase defaults to a restricted scope, which is genuine added context. It does not mention result volume, pagination, or whether the catalog is static or refreshed.

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

Conciseness3/5

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

Purpose and return shape are front-loaded, which is good. However, the ~25-item parenthetical enumeration of rail names is bloated and could be reduced to a few representative examples with an 'etc.' without losing meaning.

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

Completeness4/5

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

There is no output schema, and the description compensates by naming the fields returned and the type of operational notes included. Combined with fully documented parameters and a read-only annotation, an agent has enough to call this correctly; only filtering precedence is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and three of four parameters are enums with documented values, so the schema does the heavy lifting. The description's 'Filter by country, useCase, rail, or id' restates the schema without adding format or precedence rules (e.g. what happens when id is combined with other filters).

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 (list payment methods) plus the domain framing (bank-rail / wallet methods for AR, AP, and contractor payouts). It does not explicitly contrast with nearby reference siblings such as country_support or compliance_capabilities, but the resource itself is unambiguous.

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?

Usage is only implied: the AR/AP/payout framing suggests when a caller would reach for it, and the default useCase scope hints at a widening behavior. There is no explicit when-not-to-use guidance or pointer to an alternative catalog tool.

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