Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_balance

Read-only

Retrieve a Paystack account balance or read its ledger entries to verify available funds and track transactions; read-only and amounts are returned in subunits.

Instructions

paystack_balance. Actions: balance (read), ledger (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_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
nextNo
pageNo
actionYes
confirmNo
perPageNo
currencyNo
previousNo
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, and the description merely restates 'Read-only'. The genuinely additive statement is that amounts are positive integers in subunits, which is real behavioral context an agent would otherwise get wrong. Nothing is said about pagination behavior despite four cursor/page parameters.

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?

Three short sentences, front-loaded with actions and the most operationally important fact (subunit amounts). Minor waste from restating the tool name and the 'Read-only' claim that duplicates the annotation.

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 10-parameter, two-action tool with no output schema and zero schema documentation, the description is far too thin. The critical missing piece is the action-to-parameter mapping, which is exactly the kind of complexity the description should resolve.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description must compensate and it does not. It never explains which parameters belong to which action (currency for balance; from, to, next, previous, page, perPage, use_cursor for ledger; confirm at all), leaving the agent to guess and risk sending invalid combinations.

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 (balance) and enumerates the two operations, 'balance (read)' and 'ledger (read)', so an agent knows this covers account balance and ledger reads. It does not explicitly contrast with siblings like paystack_settlements or paystack_transactions, but the domain is unambiguous.

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?

It lists the two actions but gives no guidance on when to choose 'balance' versus 'ledger', what each returns, or any prerequisites. The agent must infer the distinction from the action names alone.

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