Skip to main content
Glama

Xonta MAX

max_validate_message

Read-onlyIdempotent

Validate a message body before sending to MAX: 4000-char text, format, keyboard limits (210/30/7, 3 per row with link/open_app/request_*), button fields and lengths, attachment combinations (≤12 media, file only with a keyboard, audio/sticker/contact alone), comment restrictions, Telegram fields left 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": {
      "body": "<body>"
    },
    "name": "max_validate_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNewMessageBody JSON: {text, format, attachments, link, notify}
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
targetNomessage — POST /messages, comment — POST /messages/{id}/commentsmessage
chat_typeNoWhere it goes, for channel-specific rules

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 declare this a safe, idempotent, non-destructive read, so safety is covered. The description goes beyond them by disclosing the actual rule set enforced (4000-char cap, 210/30/7 keyboard limits, 3-per-row with link/open_app/request_*, ≤12 media, file only with keyboard, audio/sticker/contact alone, Telegram-field leftovers), which is real behavioral content an agent cannot get from the annotations.

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?

A single front-loaded sentence puts purpose first and the rule inventory second, with no filler. It is dense to the point of being cryptic in places (bare numbers like '210/30/7' and 'request_*' assume prior knowledge), but nothing is wasted.

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

Completeness3/5

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

For a validator, the critical missing piece is what a failure looks like — whether it returns a list of violations, a pass/fail boolean, or localized messages — and no output schema exists to cover that. The rule coverage is otherwise strong for a nested body object, so the gap is narrow but real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: it reveals which body subfields are actually inspected (text, format, keyboard, attachments, comment restrictions, Telegram remnants), which is more than the schema's terse '{text, format, attachments, link, notify}'. The 'comment restrictions' clause also implicitly anchors the target=comment mode.

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?

The description opens with a specific verb and resource ('Validate a message body before sending to MAX') and immediately enumerates the rule families checked (text length, format, keyboard limits, attachment combinations, comment restrictions). An agent knows exactly what the tool does. It does not name or differentiate itself from siblings such as max_limits or max_api_reference, which keeps it from 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?

'Before sending to MAX' gives an implied usage point in a build-then-send flow, so the agent can infer when to call it. However, there are no explicit exclusions (e.g., don't call for read-only or already-validated payloads) and no named alternative for rule lookups, so routing is left to inference.

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.