Skip to main content
Glama

Xonta MAX

max_endpoint_info

Read-onlyIdempotent

Details of one MAX Bot API method (query params, body, limits, gotchas, docs link) or the full method list.

Also tells when a method was removed or restricted (GET /chats, POST /chats/{chatId}/members).

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
pathNoPath like '/messages', '/chats/{chatId}/pin' or a concrete one '/chats/-123/pin'
verbNoHTTP method: GET, POST, PUT, PATCH, DELETE. Omit to list all endpoints

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 establish this is a safe, read-only, idempotent, closed-world lookup, so the burden is lighter. The description still adds real value by disclosing what the payload contains (params, body, limits, gotchas, docs link) and that removed or restricted methods are flagged, with concrete examples (GET /chats, POST /chats/{chatId}/members). It does not say what happens when an unknown path/verb is supplied.

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 short sentences with the primary capability front-loaded and the removed/restricted-method note as a secondary line. The parenthetical endpoint examples are useful but slightly cryptic without stating why those endpoints matter (removal versus restriction).

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 read-only documentation lookup with three optional, fully described parameters and no output schema, the description supplies the missing return-content summary and the deprecation signal. The remaining gap is sibling differentiation and error behavior for invalid path/verb combinations.

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 each parameter (lang, path, verb) is already documented with format examples and defaults, including the fallback to ru / XONTA_MAX_LANG. The description adds only the implicit path-versus-catalog distinction and no syntax or format detail beyond the schema, so 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?

The description names a specific resource (a MAX Bot API method) and enumerates what the response contains: query params, body, limits, gotchas, and a docs link. It also states the second mode, the full method list, so an agent can tell the two behaviors apart. It does not distinguish itself from the sibling max_api_reference, which sounds like an overlapping reference tool, so it falls 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?

Usage is only implied: describing a single method versus the full list suggests that omitting path/verb yields the catalog, but the description never states that rule (it lives in the schema). There is no guidance on when to prefer this over max_api_reference or max_limits, which are plausible alternatives for similar information.

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.