Skip to main content
Glama

Xonta MAX

max_lint_code

Read-onlyIdempotent

Check MAX bot or mini-app code for known mistakes, with line numbers and fixes.

Finds: old host platform-api.max.ru, token in query string, 'Bearer' prefix, disabled TLS verification,
removed GET /chats, restricted member adding, type=photo uploads, wrong webhook setup (port, HTTP, /webhook),
disable_link_preview in body, plain == comparison of the webhook secret, initData signed directly with the token,
trusting initDataUnsafe, hardcoded upload hosts, Telegram leftovers. Static, never runs the code.

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": {
      "code": "<code>"
    },
    "name": "max_lint_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code of a MAX bot or mini-app (any language), or a config / curl snippet
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 the description adds genuinely new context: 'Static, never runs the code' tells the agent no code execution or side effects occur, which is stronger than readOnlyHint alone. It also discloses that findings come with line numbers and suggested fixes. It does not describe output structure or severity levels, so it falls short of a 5.

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?

The purpose sentence is front-loaded and the defect list is a scannable enumeration rather than prose. The list is long, but each item names a distinct, checkable defect rather than padding, so it largely earns its space; a slightly tighter grouping would push it higher.

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 two-parameter, no-output-schema tool, the definition covers what it does, what it never does (execute code), the kinds of input accepted, and that results include line numbers and fixes. Remaining gaps are minor: output format and how findings are structured are not stated.

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%, and the schema already explains both 'code' (source or config/curl snippet) and 'lang' (en/ru, default ru, XONTA_MAX_LANG). The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check MAX bot or mini-app code for known mistakes') and immediately enumerates the exact class of defects it detects, which separates it from siblings like max_check_webhook_secret (single concern) and max_migrate_from_telegram (rewriting rather than diagnosing). The closing note that it returns line numbers and fixes makes the output shape concrete.

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 only implied: the description makes clear it inspects code, config or curl snippets, but never says when to reach for this versus max_check_webhook_secret, max_validate_message, or max_migrate_from_telegram. No prerequisites, no exclusions, no explicit alternative routing.

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.