Skip to main content
Glama

max_mock_update

Read-only

Generate realistic MAX webhook updates for bot tests and get a curl command to POST them to your local webhook, so you can validate handling before moderation or without a token.

Instructions

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 observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety bar is lower. The description still adds value by explaining that the payload mimics the official schema, that generation works without a token/moderation, and that a curl command is emitted when a target webhook is supplied. It does not discuss reproducibility or how defaults like generated chat ids behave, leaving a small gap against the non-idempotent hint.

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, front-loaded with the primary action and artifact, followed by the test-scenario motivation. No redundant restatement of the tool name or schema, and every clause carries information.

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 usefully characterizes the return value (a schema-shaped Update plus a conditional curl command), which is the key thing an agent needs. Parameters are fully covered by the schema and safety by annotations. Only minor gaps remain, such as the exact response envelope or how conflicting overrides are resolved.

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% and every parameter (lang, text, secret, chat_id, payload, chat_type, overrides, update_type, webhook_url) is documented inline, so the schema carries the semantic load. The description adds only the framing of the two outputs and does not elaborate on overrides deep-merge behavior or update_type variants beyond what the schema already lists. Baseline 3 is appropriate.

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?

States a specific verb+resource: 'Generate a realistic MAX webhook Update for tests, shaped like the official schema'. The output artifact (a mock Update JSON, plus an optional curl command) is concrete and clearly distinct from fixture-style siblings such as max_mock_init_data or max_bridge_mock. It stops short of naming a sibling to route away from, so it lands at 4 rather than 5.

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?

Provides genuine when-to-use context: testing a bot 'before it passes moderation or without a token', which explains the intended scenario. It does not state when not to use it or point to an alternative tool, so there is no explicit routing beyond the implicit fixture-generator role.

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