Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_transfers

Destructive

List, fetch, verify, initiate, finalize, or bulk Paystack transfers with confirmation gates and preview mode for safe money movement.

Instructions

paystack_transfers. Actions: list (read), fetch (read), verify (read), initiate (money), finalize (money), bulk (money). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. 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_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
otpNo
codeNo
fromNo
nextNo
pageNo
actionYes
amountNo
reasonNo
sourceNo
statusNo
confirmNo
perPageNo
currencyNo
previousNo
recipientNo
referenceNo
transfersNo
use_cursorNo
transfer_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare a destructive, non-idempotent, open-world write surface; the description adds the critical non-annotated behavior that without the two environment flags plus confirm:true nothing is transmitted and the call degrades to a preview. It also fixes the amount unit convention (positive integers in subunits). It does not address duplicate-submission risk despite idempotentHint=false, notably for the bulk action.

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?

Front-loaded action inventory followed by the gating rules in two compact sentences, with zero filler. The terse style is efficient, though the action list packs category labels (read/money) without connecting them to which parameters each action needs.

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 20-parameter, destructive money-movement tool with no output schema and no per-parameter documentation, the description covers the safety gate but not the input contract: which parameters each action requires, how bulk transfers payloads are shaped, or what verify/fetch return. The critical precondition is present, but the definition is not complete enough to call the tool confidently without trial and error.

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?

With 20 parameters and 0% schema description coverage, the definition explains almost none of them: to, from, recipient, reason, source, status, reference, transfer_code, otp, code, currency, odata/cursor fields (use_cursor, next, previous, page, perPage) and the transfers payload for bulk are all undocumented. Only amount semantics (positive integer subunits) and confirm are clarified. The remaining nineteen parameters leave the agent guessing at format, required-per-action combinations, and reuse.

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 resource (transfers) and enumerates all six actions with a read/money classification, so an agent knows exactly what operations the tool exposes. It stops short of stating what a transfer is conceptually (a payout to a recipient) or how it differs from sibling tools like paystack_recipients or paystack_transactions, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Strong conditional guidance: writes require both confirm:true and PAYSTACK_ALLOW_WRITES=true, money actions additionally need PAYSTACK_ALLOW_MONEY_MOVEMENT=true, and otherwise the call is a preview that sends nothing. That tells the agent precisely how to invoke each class of action. It does not say when to choose transfers over alternatives such as refunds or recipients, so no explicit sibling routing.

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