Skip to main content
Glama

initialize_transaction

Accept payments by creating a Paystack transaction with customer email, amount, and reference. Set up subscriptions, splits, and payment channels.

Instructions

Initialize a transaction to accept payment on Paystack

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNoIf transaction is to create a subscription to a predefined plan, provide plan code here.
emailYesCustomer's email address
amountYesThe amount to charge in the subunit of the supported currency
bearerNoWho bears Paystack charges? account or subaccount (defaults to account).
channelsNoAn array of payment channels to control what channels you want to make available to the user to make a payment with. Available channels include: ["card", "bank", "apple_pay", "ussd", "qr", "mobile_money", "bank_transfer", "eft"]
currencyNoThe currency to charge in. Default is your integration currency.
metadataNoAdditional information to store with the transaction.
referenceYesUnique transaction reference. Only -, ., = and alphanumeric characters allowed. If not provided, a unique reference will be generated.
split_codeNoThe split code of the transaction split.
subaccountNoThe code for the subaccount that owns the payment. e.g. ACCT_8f4s1eq7ml6rlzj
callback_urlNoURL to redirect to after payment. Only required for inline payment methods.
transaction_chargeNoA flat fee to charge the subaccount for this transaction (in the subunit of the supported currency).
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states the action and purpose, but does not disclose side effects (e.g., creating a transaction record), authentication requirements, idempotency, or the need to redirect to an authorization URL after initialization.

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

Conciseness5/5

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

The description is one concise sentence, front-loaded with the verb, and contains no redundant or filler content. It is appropriately sized for a tool with rich schema documentation.

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?

Despite the tool having 12 parameters, nested objects, and no output schema, the description provides only a high-level statement. It does not explain the expected transaction flow, return values, callback/redirect behavior, or prerequisites, leaving significant gaps for an AI agent to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, meaning all 12 parameters have descriptions within the schema. The description adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 uses the specific verb 'Initialize' with the resource 'transaction' and the purpose 'to accept payment on Paystack', clearly stating what the tool does. It does not explicitly distinguish from sibling tools like charge_authorization, but the name and context make the primary action clear.

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 description provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of related tools. It is a single declarative statement without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kohasummons/paystack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server