paystack-mcp

partial_debit

Charge a partial amount from a previously authorized card, letting you debit only the needed sum from an existing authorization.

Instructions

Charge a partial amount from a previously authorized card

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": {
      "authorization_code": "<authorization_code>",
      "currency": "<currency>",
      "amount": "<amount>",
      "email": "<email>"
    },
    "name": "partial_debit"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Customer's email address
`amount`	Yes	The amount to charge in the subunit of the supported currency
`at_least`	No	Minimum amount to charge in kobo, pesewas or cents.
`currency`	Yes	The currency to charge in. Default is your integration currency.
`reference`	No	Unique transaction reference. If not provided, a unique reference will be generated.
`authorization_code`	Yes	Authorization code for the transaction

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description is the only source of behavioral context. It fails to mention important side effects such as whether the authorization is consumed, what happens if the amount exceeds the authorized balance, or any required preconditions. This is a significant gap for a financial mutation tool.

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 a single, front-loaded sentence with no filler. It delivers the core purpose efficiently, though it sacrifices detail for brevity.

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?

Given the tool's financial nature, 6 parameters, and no output schema, the description is severely under-specified. It does not explain the return value, error conditions, or prerequisite authorization status. This is inadequate for an AI agent to invoke the tool safely.

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?

The input schema provides full descriptions for all 6 parameters, so the baseline is 3. The description adds no additional meaning about the parameters, such as how the 'at_least' parameter interacts with 'amount'.

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

Purpose5/5

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

The description uses a specific verb 'charge' and identifies the resource as 'previously authorized card', clearly indicating a partial amount. This distinguishes it from the sibling 'charge_authorization' which is likely for full charges.

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

Usage Guidelines3/5

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

The description implies usage for partial charges from an authorized card, but it does not explicitly state when to use this tool over alternatives like charge_authorization, nor does it mention any exclusions or prerequisites. The context is clear but not prescriptive.

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