Skip to main content
Glama

Xonta MAX

max_migrate_from_telegram

Read-onlyIdempotent

Plan a port of a Telegram bot or Web App to MAX.

With code: every Telegram API usage with line number and the MAX replacement, features with no MAX equivalent,
effort estimate and a step-by-step plan. Without code: the full Telegram → MAX method map.

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_migrate_from_telegram"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoTelegram bot source (aiogram, python-telegram-bot, telebot, Telegraf, grammY, raw HTTP…). Omit to get only the method map
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)

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 this is a read-only, idempotent, non-networked planning operation, so the safety profile is covered. The description adds genuine behavioral detail beyond that: it discloses the exact deliverable in each mode — line-numbered API replacements, features with no MAX equivalent, effort estimate, and step-by-step plan. It omits things like output size limits or whether the code is echoed back, but this is solid.

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 tight sentences with the core action front-loaded and the two output modes clearly separated. No filler, and every clause carries information the agent needs.

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 and no required parameters, the description has to explain what comes back, and it does so for both modes. Language handling and error cases are left to the schema, which is acceptable; only a pointer to related tools 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 coverage is 100% and both parameters already document themselves, including the 'omit for method map' behavior. The description restates the code/no-code branch but adds no syntax, size, or language-selection detail beyond the schema, so the 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?

States a specific verb-plus-resource: 'Plan a port of a Telegram bot or Web App to MAX.' That is clearly distinct from the reference, scaffold, and lint siblings, and the two modes of output are spelled out. It stops short of naming any sibling tool as the alternative.

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?

The 'With code / Without code' split tells the agent how the two input modes behave, which implicitly guides usage. However, there is no explicit when-to-use versus when-to-pick-another-tool guidance (e.g., versus max_api_reference or max_scaffold_bot), and no stated preconditions or exclusions.

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.