Skip to main content
Glama

max_build_message

Read-onlyIdempotent

Builds a validated MAX POST /messages request with inline keyboard, images, and a ready curl command, so you avoid hand-writing keyboard JSON.

Instructions

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

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, read-only, idempotent, closed-world operation, so the safety burden is carried structurally. The description adds genuine value beyond that by disclosing the return contents (JSON body, validation result, curl command), which matters since there is no output schema. It does not say what happens when validation fails or whether the curl includes placeholder credentials.

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 sentences, front-loaded with the primary output, with the usage nudge placed after. No filler, no restatement of the tool name, and the colon-delimited output list is easy to scan.

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 9-parameter builder with no output schema, the description covers both the construction inputs conceptually and the shape of the return value. The remaining gap is failure behavior and whether the emitted curl is runnable as-is, which an agent would want to know before relying on the output.

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 documents lang, text, buttons, chat_id, user_id, image_urls and reply_to_mid thoroughly. The description only gestures at 'inline keyboard and images' without adding syntax or format 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?

Names a specific verb ('Build') and resource ('POST /messages request for MAX') and enumerates the artifacts produced: JSON body with inline keyboard and images, validation result, and a ready curl command. It does not name a sibling tool to differentiate from (e.g. max_validate_message, which also produces validation), so it lands just 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?

'Use it instead of hand-writing keyboard JSON' gives an implied when-to-use condition, but there is no explicit when-not-to-use guidance and no reference to the obvious alternative, max_validate_message, for validation-only needs. The agent must infer the boundary from sibling names.

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