Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_settlements

Read-only

List settlements and fetch their transactions to reconcile payouts and verify settlement details in Paystack.

Instructions

paystack_settlements. Actions: list (read), transactions (read). Read-only. 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_settlements"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
toNo
fromNo
nextNo
pageNo
actionYes
statusNo
confirmNo
perPageNo
previousNo
subaccountNo
use_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description is consistent with it. It adds one genuinely useful piece of domain context — amounts are positive integers in subunits — but says nothing about pagination behavior, the meaning of the cursor fields, or what a settlement record contains. With annotations carrying the load, a 3 fits.

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 description is compact and front-loads the action inventory followed by the units note. The only waste is the opening "paystack_settlements.", which merely restates the tool name, but it costs almost nothing.

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 12-parameter tool with no output schema and zero schema descriptions, the definition is far too thin: it explains neither the parameters nor the shape of results, and leaves the "confirm" flag ambiguous against a read-only annotation. An agent could select the tool but would be guessing at invocation.

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 12 parameters, so the description would need to compensate and does not. Filters (status, subaccount, from/to, id), pagination controls (page, perPage, use_cursor, next, previous) and especially "confirm" are left entirely unexplained — an agent cannot tell from either source what confirm does on a supposedly read-only tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and enumerates its two actions ("list", "transactions") with a read tag, which is more than a tautology. However, it never states in plain terms what a settlement is or what each action returns, so the purpose is only inferable from the action verbs rather than explained.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus siblings such as paystack_transactions or paystack_balance, nor when to pick "list" over "transactions". The only steering is the parenthetical "(read)" marker, which does not distinguish use cases.

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