Skip to main content
Glama

Xonta MAX

max_changelog

Read-onlyIdempotent

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 observed

TDQS

A3.5/5.0
Behavior3/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 safety is covered. The description adds real scope information — that the returned content is a dated changelog of breaking changes and which six areas it covers — but says nothing about ordering, date filtering, or whether non-breaking changes are included. Useful but not rich behavioral context.

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?

A single sentence, front-loaded with the core claim ('Dated MAX platform changes in 2026 that break old code') followed by a compact colon-delimited list of topics. Nothing is redundant, though the trailing list items are terse fragments whose individual meaning is only loosely conveyed.

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 simple read-only, single-optional-parameter, no-output-schema lookup tool, the description gives enough to know what content comes back and roughly when to reach for it. Remaining gaps — how to apply the findings, and whether entries can be filtered by date — are modest for this level of tool complexity.

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 one optional parameter, lang, and the schema documents it at 100% coverage including enum values and the default/fallback behavior (XONTA_MAX_LANG). The description adds no language or selection guidance beyond the schema, so the baseline 3 for high schema coverage 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 identifies a specific resource — dated 2026 MAX platform changes — and narrows it to breaking changes ('that break old code'), then itemizes the covered topics (host move to platform-api2, removed GET /chats, HTTPS-only webhooks, etc.). An agent can tell this is a changelog lookup rather than a reference or migration tool. It does not explicitly name a sibling for contrast, which keeps it just below 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?

Use is only implied: the phrase 'that break old code' hints at the scenario (checking for breaking changes during upgrade/migration), but there is no explicit when-to-use statement, no exclusion, and no pointer to alternatives such as max_api_reference for current API surface or max_migrate_from_telegram for migration steps. The agent must infer the invocation context.

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.