Skip to main content
Glama

max_scaffold_bot

Read-only

Generates a ready MAX bot project with polling dev mode, webhook prod setup, Dockerfile CA, rate limits, and text splitting. Returns files as a name-to-content map to write directly.

Instructions

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

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the return shape ('map of file name → content'), the consumer contract ('Write the files as they are'), and the out-of-band prerequisite for token creation. That is meaningful added context the annotations do not carry. It does not contradict readOnlyHint — the tool only produces content, it does not write files itself.

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 core action is front-loaded in the first sentence, followed by a parameter note and a return-value note. The feature enumeration is long but each item is a concrete capability rather than filler. Slightly dense, but no sentence is pure waste.

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 steps in to explain the return value and how to consume it, and it flags the external prerequisite for actually deploying the bot. The one gap is that the multi-language support (typescript, go) is left entirely to the schema while the prose reads as Python-only.

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%, so the schema already documents both params, making 3 the baseline. The description does add meaning for 'lang' by specifying it controls comments, README, and the bot's replies — more precise than the schema's 'Answer language'. However, it never mentions the 'language' param and the '(Python)' phrasing could mislead an agent into thinking only Python is supported, while the schema offers typescript and go.

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 things the scaffold includes (polling/webhook, Dockerfile CA, rate limits, text splitting). It is immediately distinguishable from siblings like max_api_reference or max_lint_code. It does not explicitly name a sibling to contrast against, so it stops short of a 5.

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 only implied: you use this when you need a new bot project skeleton. The description does add a real prerequisite ('Creating the bot itself and getting a token requires a verified profile on business.max.ru'), which is useful context. But there is no explicit when-not guidance or comparison to alternatives such as max_migrate_from_telegram.

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