Skip to main content
Glama
Sign In
paystack-mcp-server

paystack-mcp-server

Official
by PaystackOSS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_paystack_operation

Retrieves details about a specific Paystack API operation using its operation ID, enabling access to actions like transaction management, customer creation, and payment handling.

Instructions

Get Paystack API operation details by operation ID. Available operations are: transaction_initialize, transaction_chargeAuthorization, transaction_partialDebit, transaction_verify, transaction_list, transaction_fetch, transaction_timeline, transaction_totals, transaction_export, charge_create, charge_submitPin, charge_submitOtp, charge_submitPhone, charge_submitBirthday, charge_submitAddress, charge_check, bulkCharge_initiate, bulkCharge_list, bulkCharge_fetch, bulkCharge_charges, bulkCharge_pause, bulkCharge_resume, subaccount_create, subaccount_list, subaccount_fetch, subaccount_update, split_create, split_list, split_fetch, split_update, split_addSubaccount, split_removeSubaccount, terminal_sendEvent, terminal_fetchEventStatus, terminal_fetchTerminalStatus, terminal_list, terminal_fetch, terminal_update, terminal_commission, terminal_decommission, virtualTerminal_create, virtualTerminal_list, virtualTerminal_fetch, virtualTerminal_update, virtualTerminal_deactivate, virtualTerminal_destinationAssign, virtualTerminal_destinationUnassign, virtualTerminal_addSplitCode, virtualTerminal_deleteSplitCode, customer_create, customer_list, customer_fetch, customer_update, customer_riskAction, customer_validate, customer_initializeAuthorization, customer_verifyAuthorization, customer_deactivateAuthorization, customer_initializeDirectDebit, customer_directDebitActivationCharge, customer_fetchMandateAuthorizations, directdebit_triggerActivationCharge, directdebit_listMandateAuthorizations, dedicatedAccount_create, dedicatedAccount_list, dedicatedAccount_assign, dedicatedAccount_fetch, dedicatedAccount_deactivate, dedicatedAccount_requery, dedicatedAccount_addSplit, dedicatedAccount_removeSplit, dedicatedAccount_availableProviders, applePay_registerDomain, applePay_listDomain, applePay_unregisterDomain, plan_create, plan_list, plan_fetch, plan_update, subscription_create, subscription_list, subscription_fetch, subscription_disable, subscription_enable, subscription_manageLink, subscription_manageEmail, transferrecipient_create, transferrecipient_list, transferrecipient_bulk, transferrecipient_fetch, transferrecipient_update, transferrecipient_delete, transfer_initiate, transfer_list, transfer_finalize, transfer_bulk, transfer_fetch, transfer_verify, transfer_exportTransfer, transfer_resendOtp, transfer_disableOtp, transfer_disableOtpFinalize, transfer_enableOtp, balance_fetch, balance_ledger, paymentRequest_create, paymentRequest_list, paymentRequest_fetch, paymentRequest_update, paymentRequest_verify, paymentRequest_notify, paymentRequest_totals, paymentRequest_finalize, paymentRequest_archive, product_create, product_list, product_fetch, product_update, product_delete, storefront_create, storefront_list, storefront_fetch, storefront_update, storefront_delete, storefront_verifySlug, storefront_fetchOrders, storefront_addProducts, storefront_listProducts, storefront_publish, storefront_duplicate, order_create, order_list, order_fetch, order_product, order_validate, page_create, page_list, page_fetch, page_update, page_checkSlugAvailability, page_addProducts, settlements_fetch, settlements_transaction, integration_fetchPaymentSessionTimeout, integration_updatePaymentSessionTimeout, refund_create, refund_list, refund_retry, refund_fetch, dispute_list, dispute_fetch, dispute_update, dispute_uploadUrl, dispute_download, dispute_transaction, dispute_resolve, dispute_evidence, bank_list, bank_resolveAccountNumber, bank_validateAccountNumber, miscellaneous_resolveCardBin, miscellaneous_listCountries, miscellaneous_avs

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": {
      "operation_id": "<operation_id>"
    },
    "name": "get_paystack_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYesThe operation ID of the Paystack API endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior2/5

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

The description implies read-only behavior ('Get'), but it does not explicitly state that this operation is non-destructive or what side effects it might have. Annotations provide no additional behavioral hints (e.g., readOnlyHint, destructiveHint).

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 front-loaded with the core purpose and includes a necessary list. While the list is lengthy, it is essential. The description is otherwise concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the many available operations and the lack of an output schema, the description adequately covers the input domain but does not describe the output format or what 'operation details' includes. This leaves ambiguity about the tool's return value.

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

Parameters5/5

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

The description adds significant value by enumerating all valid operation IDs (over 100 entries), which the input schema schema only describes as 'the operation ID of the Paystack API endpoint'. This enumeration is crucial for correct invocation.

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 clearly states what the tool does: 'Get Paystack API operation details by operation ID.' The verb 'get' and resource 'operation details' are specific. However, it does not explicitly differentiate from the sibling tool 'make_paystack_request', which could cause confusion about when to use each.

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?

No guidance is provided on when to use this tool versus the sibling tool 'make_paystack_request'. The description only lists available operation IDs without contextualizing the appropriate use case.

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

Deploy Server

Other Tools