Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_transactions

Destructive

Inspect Paystack transactions—list, fetch, verify, view timelines and totals, export, or initialize and charge payments with confirmation-gated money actions.

Instructions

paystack_transactions. Actions: list (read), fetch (read), verify (read), timeline (read), totals (read), export (read), initialize (money), charge_authorization (money), partial_debit (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_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
toNo
fromNo
nextNo
pageNo
planNo
emailNo
actionYes
amountNo
statusNo
confirmNo
perPageNo
at_leastNo
channelsNo
currencyNo
customerNo
metadataNo
previousNo
referenceNo
subaccountNo
use_cursorNo
callback_urlNo
id_or_referenceNo
authorization_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely new information: the two environment gates and the fact that an ungated write is a silent preview with no request sent. It does not say what a successful money action returns or how failures surface, but the safety profile is far better disclosed than the annotations alone.

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 sentences. Density is high but every clause carries operational meaning, though the action list could be formatted more scannably.

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

Completeness3/5

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

For a 24-parameter multi-action tool with no output schema, the description covers the safety model well but omits the action-to-parameter mapping that an agent most needs. It is adequate to avoid accidental writes, less adequate to correctly compose a specific action call.

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 24 parameters, and the description compensates only for two of them: amount as a positive integer in subunits, and confirm as the write gate. Nothing maps fields like id_or_reference, authorization_code, use_cursor, at_least, or channels to the specific actions that accept them, leaving the agent to guess which parameters apply to which action.

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 enumerates all nine actions and tags each as read or money, so an agent can tell a listing call from an actual charge without opening the schema. It stops short of distinguishing this tool from siblings like paystack_refunds or paystack_transfers, which could plausibly be confused with the money actions here.

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 states the preconditions for dangerous actions (confirm:true plus PAYSTACK_ALLOW_WRITES, and PAYSTACK_ALLOW_MONEY_MOVEMENT for money), and that missing flags degrade the call to a no-op preview. What it never says is when to pick this tool over the sibling payment tools, so the routing guidance is implied rather than explicit.

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