Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_lookups

Read-only

Retrieve Paystack bank lists, supported countries and states, and resolve or verify account names for payment setup and validation.

Instructions

paystack_lookups. Actions: banks (read), resolve_account (read), countries (read), states (read), verify_account (read). Read-only. Amounts are positive integers in subunits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "paystack_lookups"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNo
pageNo
typeNo
actionYes
confirmNo
countryNo
perPageNo
currencyNo
previousNo
bank_codeNo
use_cursorNo
account_nameNo
account_typeNo
country_codeNo
document_typeNo
account_numberNo
document_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so 'Read-only' merely restates structured data. The only added claim, 'Amounts are positive integers in subunits', is oddly unanchored — the schema has no amount parameter — so it reads as boilerplate rather than disclosure. Nothing is said about rate limits, error behavior on failed account resolution, or pagination semantics.

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?

The action enumeration is front-loaded and compact, which is good. However, the trailing subunits sentence is irrelevant to this schema and consumes a fifth of already-scarce text, and the whole thing is a flat list with no grouping by action.

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 17-parameter, five-action dispatcher with no output schema, the description is far too thin: an agent cannot determine valid parameter combinations per action or what a successful response contains. It also gives no hint that some actions are paginated (page, perPage, next, previous, use_cursor) while others are not.

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

Parameters1/5

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

Schema description coverage is 0% across 17 parameters, and the description supplies no per-parameter meaning whatsoever. Critically, there is no action-to-parameter mapping, so an agent cannot tell that account_number/bank_code belong to resolve_account while country/country_code belong to states. The subunits sentence does not explain any actual parameter.

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 names the concrete resource family (lookups) and enumerates the five supported actions (banks, resolve_account, countries, states, verify_account), all marked read. An agent can tell this is reference/verification data rather than the transactional siblings. It falls short of 5 because it never explains what distinguishes resolve_account from verify_account, so two action names remain opaque.

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 at all: no indication of which action to pick for a given goal, no prerequisite (e.g., bank_code needed before resolve_account), and no explicit exclusion pointing at siblings. The only routing signal is the bare action enum.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.