Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_refunds

Destructive

List, fetch, or create Paystack refunds, with confirmation gates that prevent write or money-moving actions until explicitly allowed.

Instructions

paystack_refunds. Actions: list (read), fetch (read), create (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_refunds"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
toNo
fromNo
nextNo
pageNo
actionYes
amountNo
confirmNo
perPageNo
currencyNo
previousNo
referenceNo
use_cursorNo
transactionNo
customer_noteNo
merchant_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the dry-run/preview fallback when flags or confirm are absent, naming the exact environment flags and boolean required, and specifying that amounts are positive integers in subunits. This is precisely the extra context an agent needs before attempting a destructive money movement.

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

Conciseness5/5

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

Front-loads the action taxonomy, then the write/money guards, then the amount unit note. Every sentence carries operative information with no filler.

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 16-parameter destructive/open-world tool with no output schema, it covers safety and mode-switching thoroughly but leaves most parameter semantics unexplained and says nothing about what a successful fetch or create returns.

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%, so the description must carry parameter meaning, but it only explains action, confirm, and amount. The other thirteen parameters (id, reference, transaction, currency, page, perPage, use_cursor, next/previous, to/from, notes) are left undocumented in both schema and description.

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?

Names the resource (refunds) and enumerates the three operations with a read/money tag on each, so an agent immediately knows list/fetch are queries and create moves money. It does not contrast itself with siblings like paystack_transactions, which would be needed for 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?

Gives concrete gating conditions: writes require confirm:true and PAYSTACK_ALLOW_WRITES=true, money actions additionally require PAYSTACK_ALLOW_MONEY_MOVEMENT=true, and failure to satisfy them yields a preview with no request sent. It lacks explicit when-to-use-this-vs-another-tool routing, which keeps it below 5.

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