SpherePay MCP Server

Overview Schema Source Related Servers Discussions Admin

onboard_business_rep

Register and verify a business representative for a business customer by submitting personal details, address, and optional roles or ownership, then generating a face verification link.

Instructions

Create and verify a business representative for a business customer. Creates the representative, generates a face verification link, and submits verification. Requires customer_id (must be a business customer), first_name, last_name, email, phone, date_of_birth, and address. Optional: roles, ownership_percentage, title.

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": {
      "customer_id": "<customer_id>",
      "first_name": "<first_name>",
      "last_name": "<last_name>",
      "email": "<email>",
      "phone": "<phone>",
      "date_of_birth": "<date_of_birth>",
      "address": "<address>"
    },
    "name": "onboard_business_rep"
  }
}

Input Schema

Name	Required	Description	Default
`customer_id`	Yes
`first_name`	Yes
`last_name`	Yes
`email`	Yes
`phone`	Yes
`date_of_birth`	Yes
`address`	Yes
`roles`	No
`ownership_percentage`	No
`title`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Mar 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses three main actions (create, generate link, submit verification) but does not detail side effects, idempotency, or failure modes. Adequate but not detailed.

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

Conciseness4/5

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

Three sentences: first states purpose and steps, second lists required fields, third lists optional. No fluff, easy to parse. Could be slightly more structured but is concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters, nested address object, and output schema present, the description covers core functionality and required inputs. It does not explain the verification link outcome or error conditions, but is sufficient for basic usage.

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 0%, so description must compensate. It lists required and optional parameters and adds context (e.g., customer_id must be business customer, address as object). However, it does not elaborate on formats or constraints for fields like date_of_birth or phone.

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 clearly states the tool creates and verifies a business representative, listing the three-step process (create, generate verification link, submit verification). It distinguishes from sibling tools like 'onboard_customer' and 'verify_customer' by specifying it's for a business customer's representative.

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

Usage Guidelines4/5

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

The description provides clear context: it requires a customer_id that must be a business customer, and lists required and optional fields. It does not explicitly state when not to use or compare to alternatives, but the purpose implies the use case.

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