SpherePay MCP Server

Overview Schema Source Related Servers Discussions Admin

list_customers

Retrieve a paginated list of SpherePay customers. Specify page and limit to navigate customer records for onboarding and account management.

Instructions

List SpherePay customers with pagination. Returns paginated customer list.

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": "list_customers"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Mar 21, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like read-only nature, authentication requirements, or rate limits. The tool name suggests a read operation, but this is not confirmed.

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

Conciseness3/5

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

The description is short but contains redundancy: 'List SpherePay customers with pagination. Returns paginated customer list.' The two sentences convey essentially the same information. Could be combined into one clear sentence.

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 simplicity (2 parameters, no requirements), the description is incomplete. It does not describe the output structure (though an output schema exists) or any filtering options. An AI agent would benefit from knowing the response format or default behavior.

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

Parameters2/5

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

The schema has no descriptions for 'page' and 'limit' (0% coverage). The description merely mentions 'pagination' but does not explain their meaning, valid ranges, or defaults beyond the schema defaults.

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 the tool lists customers and mentions pagination. It is specific to 'SpherePay customers' and distinguishes from sibling 'get_customer' by implying a list. However, it could be more explicit about what differentiates this from other list tools like list_bank_accounts.

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 alternatives such as 'get_customer' or other list functions. The description lacks any context about prerequisites or when not to use it.

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