Skip to main content
Glama

Xonta MAX

max_mock_update

Read-only

Generate a realistic MAX webhook Update for tests, shaped like the official schema, plus a curl command to send it to your local webhook. Lets you test a bot before it passes moderation or without a token.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textNoMessage text (message_created/edited, comments) or new title
secretNoWebhook secret to put into X-Max-Bot-Api-Secret
chat_idNoChat id; default is generated
payloadNoCallback payload or bot_started deep link payload
chat_typeNoWhere it happensdialog
overridesNoDeep-merge into the generated update
update_typeYesmessage_created, message_callback, bot_started, bot_added, bot_removed, message_edited, message_removed, user_added, user_removed, comment_created, chat_title_changed, dialog_muted, bot_admin_permissions_changed, …
webhook_urlNoIf set, also returns a curl command that POSTs the update there

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with that: it produces a payload and a curl string rather than sending anything itself. It adds genuine context beyond the annotations by disclosing the two-part return (schema-shaped update plus optional curl command) and the tokenless pre-moderation use case. It could still say more about whether the generated update is deterministic or random, given idempotentHint=false.

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

Conciseness5/5

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

Two sentences, both load-bearing, with the primary output stated first and the secondary curl artifact second. There is no filler and no restatement of the name or title.

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?

For a nine-parameter generator with no output schema, the description adequately explains what comes back and under what condition the curl command appears, which is the main thing an agent needs. The remaining details — enum values, defaults, override merging — are fully covered by the rich schema, so nothing critical is missing.

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%, with every one of the nine parameters documented in the schema itself, including the language default, the webhook_url curl behavior and the overrides deep-merge. The description adds no parameter-level detail beyond what is already structured, so the baseline of 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 names a specific verb and artifact: generate a realistic MAX webhook Update shaped like the official schema, plus a curl command for local delivery. That is far more precise than the name alone. It stops short of distinguishing itself from adjacent mock tools such as max_mock_init_data or max_bridge_mock, so an agent cannot route between them from this text alone.

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

Usage Guidelines3/5

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

It gives a real motivating context — testing a bot before moderation approval or without a token — which implies when the tool is appropriate. However, it never states when not to use it, nor names an alternative among the mock/bridge siblings, so selection guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.