Skip to main content
Glama

Xonta MAX

max_deeplink

Read-onlyIdempotent

Build and validate MAX deep links. 'share' gives a link, an HTML button and a JS helper that open MAX's chat picker with prefilled text — works on any website or AI agent output without owning a bot. Payload limits are checked, because MAX silently drops payloads that are too long or have bad characters.

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": {
      "kind": "<kind>"
    },
    "name": "max_deeplink"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesstart — open bot with payload; startapp — open mini-app; share — 'send to MAX' link for any site, no bot needed; mention — user mention markup
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textNoshare: text to prefill; mention: display name
payloadNostart: ≤128 chars; startapp: ≤512, A-Za-z0-9_- only
user_idNomention: MAX user id
bot_nameNoBot public name as in max.ru/<name> (start, startapp)
button_labelNoshare: label for the generated HTML button; default depends on lang

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description goes beyond them by disclosing payload validation behavior ('MAX silently drops payloads that are too long or have bad characters') and by naming the return artifacts for share (link, HTML button, JS helper), which is valuable since 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 sentences, each productive: purpose first, the highest-value mode next, the silent-failure warning last. There is no filler or repetition of the enum values already present in the schema.

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 7-parameter tool with no output schema, the description explains what only the 'share' kind returns and says nothing about what start/startapp/mention produce. Combined with the absence of any when-to-use framing beyond share, it is adequate but leaves gaps an agent would hit when calling the other kinds.

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 every parameter already carries its own documentation, including the payload length and charset rules. The description mostly restates that payload limits exist rather than adding format or constraint detail beyond the schema; 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?

The description opens with a specific verb and resource: 'Build and validate MAX deep links.' It then explains the 'share' variant in concrete terms ('an HTML button and a JS helper that open MAX's chat picker'). It stops short of naming any sibling tool, so an agent must rely on the schema's kind enum to understand the other three modes.

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 context exists only for the 'share' mode: it notes the link 'works on any website or AI agent output without owning a bot.' There is no guidance on when to pick start/startapp/mention, no prerequisites, and no mention of alternatives such as max_tracking_links or max_build_message.

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.