paystack-mcp

disable_transfers_otp

Disable the OTP requirement for transfers in Paystack. This eliminates the one-time password step, simplifying transfer automation and reducing manual intervention for bulk payouts.

Instructions

Disable OTP requirement for transfers

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "disable_transfers_otp"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only states the action but does not mention side effects, reversibility, required permissions, or whether it requires confirmation. For a security-sensitive mutation like disabling OTP, this is a major gap.

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 fluff. Every word contributes to the meaning, making it appropriately concise and easy to parse.

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 simplicity of the tool (no params, no output schema), the description is minimal but omits crucial context. It does not explain the relationship with sibling tools like 'finalize_disable_otp' or 'enable_transfers_otp', nor does it cover prerequisites or consequences of disabling OTP. This makes it incomplete for informed use.

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

Parameters4/5

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

The tool has zero parameters, so the schema provides no information. The description adds no parameter details, but since none exist, the baseline of 4 applies. No additional semantic explanation is needed.

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 'Disable OTP requirement for transfers' uses a clear verb and resource, stating exactly what the tool does. However, it does not distinguish itself from the sibling tool 'finalize_disable_otp', which likely relates to completing the disable process. This ambiguity prevents a perfect score.

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

Usage Guidelines1/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 alternatives. The description does not mention any prerequisites, sequencing (e.g., whether this is the first step before 'finalize_disable_otp'), or scenarios where this tool is appropriate. Users are left without context.

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