Skip to main content
Glama

Xonta MAX

max_build_message

Read-onlyIdempotent

Build a correct POST /messages request for MAX: JSON body with inline keyboard and images, validation result and a ready curl command. Use it instead of hand-writing keyboard JSON.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textNoMessage text, up to 4000 characters
formatNoText markup
buttonsNoRows of buttons. Short form: {text, payload} → callback, {text, url} → link, {text, web_app, payload?} → open_app; or full {type, text, ...}
chat_idNoFor the curl example
user_idNoFor the curl example, private dialog
image_urlsNoExternal image URLs to attach without uploading
reply_to_midNoReply to this message id
disable_link_previewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, which matches a pure request-builder. The description adds useful shape about what comes back (JSON body, validation result, curl command) for a tool with no output schema, but it says nothing about how validation failures are surfaced or what happens with partial/invalid buttons.

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?

Two compact sentences, front-loaded with the concrete deliverable and followed by the differentiator. Every clause carries information; the only cost is that the first sentence is a dense list that reads as a run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter builder with high schema coverage and no output schema, the description covers purpose, return contents, and usage alternative. Nothing an agent needs in order to call it correctly appears to be 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 description coverage is 89%, so the schema already explains lang, text, format, buttons short forms, chat_id/user_id, and image_urls. The description only alludes to inline keyboards and images in general terms and adds no syntax or format detail beyond the schema; the baseline of 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 and artifact: builds a POST /messages request body for MAX with inline keyboard, images, a validation result, and a curl command. That is far more specific than the name alone. It does not explicitly distinguish itself from max_validate_message, even though it mentions producing a 'validation result', so an agent must infer the boundary.

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?

"Use it instead of hand-writing keyboard JSON" gives an explicit when-to-use rule against the manual alternative. It offers no when-not guidance and does not route to sibling tools such as max_validate_message or max_api_reference, so the exclusion side is missing.

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.