ChatPush MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create sub-customer

create_sub_customer

Creates a separate ChatPush sub-client account for a new platform client, returning its own API token to save for onboarding.

Instructions

Create a sub-client under your ChatPush multi-customer account. The response contains the sub-customer's own API token — it is shown only here, so save it.

Use it when onboarding a new client of a platform built on ChatPush: each sub-customer gets a separate account, its own messengers and its own subscription.

Requires a multi-customer account: a ChatPush client that may create sub-clients through the API.

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": {
      "name": "<name>"
    },
    "name": "create_sub_customer"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the sub-customer, e.g. the client's company name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the description is not carrying the safety profile. It still adds real value beyond them: the API token is returned only once (irrecoverable if lost) and the calling account must be a multi-customer account, a permission constraint the annotations do not express.

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?

The most important information, the one-time token, is front-loaded, and each paragraph has a distinct job (action, use case, prerequisite). The third paragraph partly restates the multi-customer account framing from the first sentence, which is mild redundancy.

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

Completeness4/5

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

With no output schema, the description correctly fills that gap by explaining that the response contains the sub-customer's API token. A create operation with no annotations for permissions is well served by the stated account requirement; minor omissions include duplicate-name behavior and whether the sub-customer is immediately active.

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?

With a single parameter at 100% schema description coverage, the schema already documents "name" with an example, so the baseline is 3. The description adds no further semantics about the name field, such as uniqueness constraints or character handling.

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 opens with a specific verb and resource ("Create a sub-client under your ChatPush multi-customer account") and the scope is unambiguous. The create verb inherently separates it from siblings like list_sub_customers and get_sub_customer, which operate on existing sub-customers.

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?

It states the scenario explicitly: "Use it when onboarding a new client of a platform built on ChatPush," and names a hard prerequisite ("Requires a multi-customer account"). There is no explicit when-not guidance or named alternative, but no other tool in the sibling list creates sub-customers, so the routing ambiguity is minimal.

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