Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_recipients

Destructive

List, fetch, create, update, or delete Paystack transfer recipients. Enables managing recipient records and bank details with confirmation-gated writes before any transfer.

Instructions

paystack_recipients. Actions: list (read), fetch (read), create (write), update (write), delete (write). 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_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
codeNo
fromNo
nameNo
nextNo
pageNo
typeNo
emailNo
actionYes
confirmNo
perPageNo
currencyNo
previousNo
bank_codeNo
use_cursorNo
descriptionNo
account_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the crucial dry-run behavior: without the required flags the call is a preview and no request is sent. It also states the amount unit convention (positive integers in subunits), which is real behavioral context an agent cannot get from structured fields. It stops short of saying what delete destroys or whether deletes cascade to scheduled transfers.

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 action list is front-loaded and the gating rules follow in priority order with no filler. The leading 'paystack_recipients.' merely restates the tool name and could be dropped, but the rest is dense and earns its space.

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 multiplexed tool with destructive writes, no output schema, and zero schema descriptions, the definition covers the safety gating well but leaves the parameter-to-action mapping entirely unexplained. An agent still cannot tell which fields are required to create a recipient or what identifier a delete needs.

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 17 parameters, so the description carries the full burden, yet it only explains `action` and `confirm` semantics plus the subunit convention for amounts. It says nothing about which parameters belong to create versus update versus fetch/delete, nor about code, account_number, bank_code, currency, use_cursor, next/previous, page/perPage, or the to/from/name/email/type fields.

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 (Paystack recipients) and enumerates all five actions with a read/write tag on each, so an agent knows exactly what operations exist. It does not differentiate itself from siblings such as paystack_transfers, which is the most likely source of confusion for recipient-vs-transfer routing.

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?

It clearly explains the precondition path for writes (confirm:true plus PAYSTACK_ALLOW_WRITES, and PAYSTACK_ALLOW_MONEY_MOVEMENT for money actions), which effectively tells the agent when a call will actually execute. However, it gives no guidance on when to pick this tool over paystack_transfers or paystack_lookups, and no guidance on choosing among the five actions beyond their read/write labels.

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