ChatPush MCP Server

Official

by ChatPush

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get sub-customer

get_sub_customer

Read-only

Retrieve a sub-customer by customer_id to check subscription status, expiry, and WhatsApp/Telegram connection status; optionally reveal full tokens.

Instructions

Show one sub-client by its customer_id: subscription status and expiry, and whether WhatsApp and Telegram are connected.

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

Input Schema

Name	Required	Description	Default
`customer_id`	Yes	Internal ChatPush ID of the sub-customer.
`include_tokens`	No	Show the full sub-customer tokens. Default false: tokens are masked.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's added value is the account-type precondition, which is real behavioral context an agent cannot get from annotations or schema. It stops short of noting that token values are masked by default, leaving that to the schema.

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?

Two short sentences with the retrieval scope and returned fields front-loaded, then the prerequisite. No redundant restatement of the name or title; the clause defining a multi-customer client is slightly verbose but earns its place as a gating condition.

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 does the useful work of naming what comes back (subscription status/expiry, channel connection flags). For a two-parameter read-only tool with full schema coverage, that plus the account prerequisite is nearly enough; only the masking behavior of include_tokens is left implicit.

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 both parameters (customer_id and include_tokens) are already documented in the schema, including the masking default. The description reinforces customer_id's role but adds no meaning beyond the schema for include_tokens; baseline 3 applies.

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 and resource ("Show one sub-client by its customer_id") and enumerates the returned fields (subscription status and expiry, WhatsApp/Telegram connection state). It implicitly separates itself from the plural list_sub_customers by emphasizing a single record, though it never names that sibling explicitly.

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 a concrete prerequisite: the caller must be a multi-customer ChatPush client that can create sub-clients via the API, which tells an agent when this tool is available. It does not explicitly contrast with list_sub_customers for discovery-style lookups, so routing is inferred rather than spelled out.

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