Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_invoices

Destructive

Manage Paystack invoices: list, fetch, create, update, verify, notify, finalize, archive, or get totals. Writes and money actions require confirmation and env flags; otherwise preview only.

Instructions

paystack_invoices. Actions: list (read), fetch (read), create (write), update (write), verify (read), notify (write), finalize (write), archive (write), totals (read). 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_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
toNo
fromNo
nextNo
pageNo
draftNo
actionYes
amountNo
statusNo
confirmNo
perPageNo
currencyNo
customerNo
due_dateNo
previousNo
line_itemsNo
use_cursorNo
descriptionNo
send_notificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=true, non-idempotent), the description usefully discloses the read/write split per action and the preview fallback when confirmation or environment flags are absent. It does not say whether archived/finalized invoices are reversible, what the preview returns, or what permission scope is needed for the money-movement gate, so meaningful behavioural gaps remain for a destructive mutation tool.

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 compact and front-loaded, and the gating rules follow in priority order with zero filler. The only waste is the opening repetition of the tool name, which the caller already has.

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 9-action, 19-parameter mutation tool with no output schema and no annotation coverage of the gating logic, the description covers safety preconditions well but omits any per-action parameter mapping or return expectations. An agent can decide whether it is allowed to call the tool, but not how to shape most calls correctly.

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 19 parameters, and the description only explains two of them: confirm (boolean) and amount ('positive integers in subunits'). Nothing maps the remaining parameters (id, customer, currency, line_items, status, due_date, page/perPage/use_cursor, draft, send_notification, previous/next, to/from) to the actions that consume them, leaving the agent to guess which fields belong to create vs update vs totals.

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 definition names the resource (invoices) and enumerates all nine actions with a read/write tag on each, so an agent knows exactly which operations are available. It stops short of stating what an invoice object is or summarising the tool's overall role, but the action inventory is specific enough to distinguish this from siblings such as paystack_transactions or paystack_refunds.

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?

It gives concrete preconditions for the write paths: confirm:true plus PAYSTACK_ALLOW_WRITES=true, and PAYSTACK_ALLOW_MONEY_MOVEMENT=true for money actions, with the important consequence that unmet flags turn the call into a preview. That is strong when-to-use context, but it never contrasts this tool with sibling read/write toolkits, so there is no explicit alternative routing.

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