Skip to main content
Glama

max_migrate_from_telegram

Read-onlyIdempotent

Plan migration of a Telegram bot or Web App to MAX: map Telegram API calls to MAX replacements, identify unsupported features, and outline effort estimates and a step-by-step plan.

Instructions

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 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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value beyond that by specifying the shape of the deliverable — line numbers, MAX replacements, unmapped features, effort estimate, step-by-step plan — which matters because there is no output schema.

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?

Three short segments: purpose first, then the two modes in parallel structure. No filler, no repetition, and the code-present branch is front-loaded.

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 two-parameter, read-only planning tool with no output schema, the description discloses enough of the return content for an agent to pick it confidently. Minor gaps remain around input limits and how the lang parameter affects the answer, but the schema covers the latter.

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 carry descriptions, including the 'omit to get only the method map' behavior. The description's 'with code / without code' split largely restates that, and it says nothing about the lang parameter or any constraints on code size or language support.

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: 'Plan a port of a Telegram bot or Web App to MAX', which no sibling (scaffold_bot, api_reference, lint_code) covers. It never names an alternative sibling to route against, so it lands at clear-but-not-sibling-differentiated.

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?

Gives explicit operating context through the two input modes: passing source code yields a line-by-line migration plan, omitting it yields only the method map. That tells an agent how to invoke it for each intent, but there is no statement of when to prefer max_api_reference or max_scaffold_bot instead.

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