Skip to main content
Glama

Xonta MAX

max_limits

Read-onlyIdempotent

All MAX platform limits in one table: text length, rate limits, keyboard size, attachments, file sizes, deep link payloads, webhook rules, bots per profile — each with a source link. Also update types, button types, errors.

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

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
Behavior4/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 the safety profile is covered. The description adds genuine context beyond that: it discloses the return shape in part ('all limits in one table ... each with a source link') and scopes the coverage so the agent knows additional categories like update types, button types, and errors are included. It does not mention caching/staleness or result size, which is a minor gap for a static reference dump.

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 sentences, front-loaded with the main promise ('All MAX platform limits in one table') followed by a coverage list. The enumeration is dense but each item earns its place by telling the agent what questions this tool answers. No filler or restatement of the name.

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?

This is a simple, zero-required-parameter read tool with rich annotations and a fully documented schema. The main thing an agent needs — what content is inside and that entries carry source links — is stated. Only minor details such as output format and whether the table is static or fetched live are missing, and no output schema exists to cover them.

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 with full schema coverage, including its default and the XONTA_MAX_LANG environment fallback. The description says nothing further about language selection, so the schema carries the entire burden. With 100% coverage the baseline of 3 is appropriate.

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 platform limits) and enumerates exactly what is covered — text length, rate limits, keyboard size, attachments, file sizes, deep links, webhooks, bots per profile — plus update/button types and errors. It is immediately clear this is a reference/lookup tool rather than a builder or validator. It stops short of stating an explicit verb ('returns a table of...') or naming how it differs from max_api_reference, which keeps it at 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to reach for this tool versus related siblings such as max_api_reference, max_split_text, or max_validate_message. Usage is only implied by the content list (look something up before building or validating). No prerequisites, no exclusions, no 'use this instead of' 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.