Skip to main content
Glama

Xonta MAX

max_scaffold_bot

Read-only

Generate a ready MAX bot project: polling for dev, webhook for prod, the Russian Trusted Root CA in the Dockerfile, chat tracking without GET /chats, callback answers, constant-time secret check, rate limits and text splitting (Python). lang sets the language of comments, README and the bot's replies.

Returns a map of file name → content. Write the files as they are. Creating the bot itself and getting a token
requires a verified profile on business.max.ru.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "max_scaffold_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
languageNopython (httpx, no official SDK), typescript (@maxhub/max-bot-api) or go (official client v2)python

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that: it only returns a map of file name → content and tells the caller to write the files themselves. It adds genuinely useful context beyond the annotations — the exact return shape, the write-it-yourself instruction, and the external prerequisite that creating the actual bot and obtaining a token requires a verified business.max.ru profile.

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 output/behavior statement is front-loaded in the second paragraph, and the feature list is dense but each item is concrete. Slightly cramped by the parenthetical '(Python)' qualifier, which creates the ambiguity noted above rather than earning its place as written.

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 compensates by specifying the return value as a file name → content map and stating that files should be written verbatim. The external prerequisite is covered; what remains thin is whether the feature set differs per target language.

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 coverage is 100% and both parameters carry enums, so the baseline is 3. The description does add meaning for lang (it governs comments, README and the bot's replies, not just replies), but it never disambiguates `lang` from `language`, and the feature list is tagged '(Python)' while `language` accepts typescript and go — leaving unclear which listed features apply to the non-Python variants.

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 and resource — 'Generate a ready MAX bot project' — and enumerates the concrete scaffolding concerns (polling/webhook, CA cert, chat tracking, rate limits, text splitting). The purpose is unmistakable and clearly distinct in kind from reference/lint/migration siblings, though no sibling is named explicitly.

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?

Usage is implied rather than stated: 'Write the files as they are' tells the caller what to do with the output, and the business.max.ru verified-profile note gives a prerequisite. There is no explicit when-to-use versus alternatives such as max_migrate_from_telegram (for porting an existing bot) or max_lint_code.

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.