Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_customers

Destructive

Manage Paystack customer records: list, fetch, create, update, validate, or set risk action. Write operations require confirmation; otherwise requests are preview-only.

Instructions

paystack_customers. Actions: list (read), fetch (read), create (write), update (write), validate (write), set_risk_action (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_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
bvnNo
codeNo
fromNo
nextNo
pageNo
typeNo
emailNo
phoneNo
actionYes
confirmNo
countryNo
perPageNo
customerNo
metadataNo
previousNo
bank_codeNo
last_nameNo
first_nameNo
use_cursorNo
middle_nameNo
risk_actionNo
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 (destructiveHint=true, readOnlyHint=false), the description discloses a genuinely important behavior: without the flags the call is a preview and no request is sent. That is high-value context an agent could not infer from the annotations. It does not say which of the write actions are actually destructive or what side effects follow a successful write.

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 with read/write tags is front-loaded and easy to scan, and the gating rules follow in a logical order. The closing sentence about amounts is dead weight for this schema and slightly dilutes an otherwise tight definition.

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 23-parameter, multi-action tool with no output schema and zero schema descriptions, the description should map fields to actions (which fields create needs, what validate requires, what pagination params apply to list). It provides none of that, so an agent must guess which parameters belong to which action.

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 23 parameters at 0% schema description coverage, the description must carry the parameter burden, but it only explains 'confirm' (implicitly) and amounts. Worse, the sentence 'Amounts are positive integers in subunits' refers to a field that does not exist in this schema, so it adds no meaning and may mislead. Domain fields like bvn, bank_code, account_number, risk_action, and the cursor/pagination params are left entirely unexplained.

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 customers) and enumerates all six actions with a read/write tag on each, so an agent knows exactly what operation surface exists. It stops short of describing what individual actions do (e.g., what 'validate' checks or what 'set_risk_action' changes), and it never distinguishes this from sibling tools like paystack_transactions.

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?

Usage conditions for write actions are stated concretely: confirm:true plus PAYSTACK_ALLOW_WRITES=true, and PAYSTACK_ALLOW_MONEY_MOVEMENT=true for money actions. However, there is no guidance on which action to pick for a given task, no prerequisites for read actions, and no alternatives named.

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