Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

paystack_catalog

Read-only

List and fetch Paystack subaccounts, plans, subscriptions, products, and pages for read-only catalog inspection and retrieval.

Instructions

paystack_catalog. Actions: list_subaccounts (read), fetch_subaccount (read), list_plans (read), fetch_plan (read), list_subscriptions (read), fetch_subscription (read), list_products (read), fetch_product (read), list_pages (read), fetch_page (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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
codeNo
nextNo
pageNo
planNo
actionYes
confirmNo
perPageNo
customerNo
previousNo
use_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so 'Read-only' in the description earns no extra credit. The one piece of added value is 'Amounts are positive integers in subunits', which prevents unit errors in returned data; however, nothing is said about pagination, cursor behavior, or what a fetch_* call needs when the record is missing.

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

Conciseness3/5

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

It is a single dense sentence: the ten-action list is useful and front-loaded, but the leading 'paystack_catalog.' merely repeats the tool name, and the action list is presented as an undifferentiated run rather than grouped by resource with a read/write label. It is economical but not optimally structured.

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?

This is an 11-parameter multiplexer with no output schema and no per-parameter documentation, yet the description covers neither parameter applicability per action nor pagination semantics. For a tool this complex, the definition leaves the agent materially under-informed before its first call.

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 11 parameters, so the description must compensate and largely does not. Only the enum of actions is reflected; id, code, plan, customer, next, previous, page, perPage, use_cursor and confirm are never explained, leaving the agent to guess which identifiers apply to which action and how cursor pagination is driven.

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 family (subaccounts, plans, subscriptions, products, pages) and enumerates all ten operations, so an agent knows exactly what capability is behind the tool. It falls short of a 5 because the grouping is a grab-bag and nothing distinguishes it from sibling tools like paystack_customers or paystack_transactions beyond the subject nouns.

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?

The action list is an operation menu, not usage guidance: there is no statement of when to call this versus a sibling tool, no guidance on choosing list_* versus fetch_*, and no note on which parameters each action requires. The only directive is the implicit 'pick one of these ten actions'.

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