Skip to main content
Glama

Xonta MAX

max_convert_formatting

Read-onlyIdempotent

Convert formatted text to MAX markup: Telegram MarkdownV2 (underline x → ++x++, unescape), Telegram HTML (tg://user → max://user, spoilers dropped) or ordinary Markdown from an LLM (lists → bullets, rules removed). Reports what MAX cannot show (spoilers, tables, lists, inline images). Use the returned format value in the body.

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": {
      "text": "<text>",
      "source": "<source>"
    },
    "name": "max_convert_formatting"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textYesFormatted text
sourceYesWhere the text comes from; 'markdown' = ordinary Markdown (e.g. LLM output)
targetNoMAX format to producemax_markdown

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 establish read-only, idempotent, non-destructive behavior, so the description's job is to add transformation semantics — and it does: underline maps __x__ → ++x++, tg://user → max://user, spoilers are dropped, and lists/rules are rewritten. It also warns that unsupported constructs (spoilers, tables, lists, inline images) are reported, which is meaningful lossiness disclosure. It stops short of describing exact error behavior or edge cases.

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?

Three dense sentences with the core action front-loaded and the downstream instruction last. The parenthetical conversion examples are informative but packed into long clauses; a light list would scan faster. No filler or restated title text.

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?

There is no output schema, so the description usefully discloses that a 'format' value is returned and that unsupported constructs are reported — enough for an agent to chain the call correctly. The distinction between the two MAX targets is left entirely to the schema enum, which is acceptable given full coverage, but a hint about when max_html vs max_markdown matters would close the remaining gap.

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%, so the schema already documents all four parameters including enum meanings and the lang default. The description reinforces the meaning of the 'source' values with concrete examples (LLM output as Markdown) but adds no syntax or format detail beyond the schema. 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 and resource — 'Convert formatted text to MAX markup' — and enumerates the three accepted sources (Telegram MarkdownV2, Telegram HTML, ordinary Markdown) plus the two MAX targets. An agent can tell this is a format transformer rather than a builder or validator. It does not name sibling tools such as max_build_message or max_validate_message, so differentiation is inferred rather than stated.

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 by the source examples ('ordinary Markdown from an LLM') and by the closing instruction 'Use the returned format value in the body,' which tells the agent what to do with the result. However, there is no explicit when-to-use vs when-not-to-use statement or named alternative for cases like constructing a message from scratch.

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.