paystack-mcp

transaction_totals

Obtain the total received amount by fetching transaction records, with optional date filtering and pagination controls.

Instructions

Get total amount received on your account

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": {
      "perPage": "<perPage>",
      "page": "<page>"
    },
    "name": "transaction_totals"
  }
}

Input Schema

Name	Required	Description
`to`	No	A timestamp at which to stop listing transaction e.g. 2016-09-24T00:00:05.000Z
`from`	No	A timestamp from which to start listing transaction e.g. 2016-09-24T00:00:05.000Z
`page`	Yes	Page number to retrieve. Default is 1.
`perPage`	Yes	Number of records to retrieve per page. Default is 50.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. 'Get' implies a read operation, but there is no mention of authentication needs, how 'from'/'to' filters affect the total, whether pagination parameters are used for aggregation, or what 'received' means (e.g., only successful transactions). This minimal disclosure is insufficient.

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, clear sentence with zero unnecessary words. It is appropriately sized for the tool's core function and front-loads the essential purpose.

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?

There is no output schema and no annotations. The description explains the purpose but fails to address critical gaps: how filters and pagination affect the total, what the return value looks like, and why pagination parameters are required for an aggregate total. This incompleteness is significant for a tool with 4 parameters.

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?

Input schema coverage is 100% with all four parameters well-described, so the baseline is 3. The description adds no additional parameter semantics beyond the schema, which is acceptable given high schema coverage.

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 a specific verb 'Get' and identifies a clear resource: 'total amount received on your account'. This clearly states the tool's purpose. However, it does not explicitly distinguish it from sibling tools like check_balance or list_transactions, earning a 4 rather than a 5.

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. It simply states what it does without context, exclusions, or mentions of prerequisites, leaving the agent to infer usage.

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