Skip to main content
Glama

max_endpoint_info

Read-onlyIdempotent

Retrieve MAX Bot API endpoint details—query parameters, request body, limits, gotchas, and docs—or list methods and flag removed/restricted routes.

Instructions

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: the payload contents (limits, gotchas, docs link) and, importantly, that it surfaces removal or restriction status for specific endpoints. It does not mention caching, pagination, or response size for the full-list mode.

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 output content front-loaded before the deprecation note. The parenthetical example paths are useful and cheap. Minor cost: the second sentence is a fragment separated by a line break, which reads slightly disjointed.

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 reference lookup with no output schema, the description does the necessary work by listing the categories of information returned and flagging deprecation/restriction coverage. Nothing essential for a correct call is missing. It could still say more about the shape of the full-list response.

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 lang, path and verb are already documented with examples and the default-language rule. The description adds only the framing that omitting filters yields the full list, which is already in the verb parameter description. Baseline 3 applies when the schema carries the parameter burden.

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 (MAX Bot API method details) and enumerates exactly what is returned: query params, body, limits, gotchas, docs link. It also makes clear the tool has two modes: one method versus the full method list. It does not distinguish itself from the sibling max_api_reference, which sounds closely related, so an agent cannot fully resolve the overlap from the text alone.

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 'or the full method list' phrasing suggests omitting filters to enumerate, and the schema repeats that for verb. There is no explicit statement of when to prefer this over max_api_reference or max_limits, and no stated prerequisites. Adequate but leaves the agent to infer routing between similar reference tools.

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