Skip to main content
Glama

max_changelog

Read-onlyIdempotent

Lists dated 2026 MAX platform changes that break old code, including API host moves, removed endpoints, webhook and access restrictions, so you can update bots and mini-apps.

Instructions

Dated MAX platform changes in 2026 that break old code: host move to platform-api2, removed GET /chats, restricted member adding, HTTPS-only webhooks, comments API, self-employed access.

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

Input Schema

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

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real scoping information beyond that: only breaking changes, only 2026, with a concrete inventory of topics. It says nothing about return volume, structure, or whether deprecated-but-working changes are included.

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?

One dense sentence, front-loaded with the qualifier ('dated... 2026 that break old code') before the item list. The enumeration is compact and informative rather than padding; a slightly cleaner verb phrase would make it fully tight.

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 static reference tool with no output schema and a fully documented parameter, the description tells the agent what domain of content to expect, which is close to sufficient. It still leaves the response shape and completeness unstated, so an agent cannot predict whether it receives brief summaries or full migration details.

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?

There is a single optional lang parameter and the schema documents it fully (en/ru, default ru, environment override), so the schema carries the burden at 100% coverage. The description adds nothing about language handling, which is acceptable but not additive.

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 gives a specific resource (dated MAX platform changes in 2026) and narrows it to breaking changes, then enumerates the covered items (host move to platform-api2, removed GET /chats, webhook HTTPS, etc.). That is far more concrete than the name alone. It stops short of distinguishing this from siblings like max_api_reference or max_migrate_from_telegram, which an agent must infer.

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 implied rather than stated: an agent can infer this is the 'what broke recently' reference to consult when code stops working or when migrating. There is no explicit when-to-use, no when-not-to-use, and no pointer to max_api_reference or max_migrate_from_telegram as alternatives.

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