Paymenter MCP Server

paymenter_create_user

Create a new customer account in Paymenter by submitting email and password, with optional profile and role details. Use it to register users for billing and hosting services.

Instructions

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": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "paymenter_create_user"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	User email address
`role_id`	No	Role ID (e.g. administrator role ID)
`password`	Yes	Account initial password
`last_name`	No	Last name
`first_name`	No	First name
`email_verified_at`	No	ISO 8601 timestamp for email verification

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose required permissions/role, whether a verification email is sent (relevant given the email_verified_at field), what happens on duplicate email, or whether the created account is returned. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

A single short, front-loaded sentence with no filler or redundancy. It is appropriately sized, though its terseness is partly why behavioral and contextual gaps remain.

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?

For a 6-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits permission requirements, duplicate-email behavior, side effects like verification emails, and any sense of the return value, leaving the agent without the context needed to call it 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?

Schema description coverage is 100%, so each of the 6 parameters is already documented in the schema, establishing a baseline of 3. The description adds no extra meaning about field semantics (e.g., what role_id controls or how email_verified_at is handled), so it does not exceed the baseline.

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 states a specific verb (register/create) and resource (new customer account) plus the system (Paymenter), which is clear enough to act on. It does not explicitly differentiate from siblings like paymenter_update_user or paymenter_delete_user, but the 'new customer account' phrasing implicitly signals creation rather than mutation of an existing user.

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?

There is no guidance on when to use this versus alternatives (e.g., update_user), no preconditions such as requiring unique email or admin privileges, and no exclusions. The agent must infer usage entirely from the tool name.

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

Deploy Server