Skip to main content
Glama

max_limits

Read-onlyIdempotent

Look up MAX platform limits and API rules in one table: text length, rate limits, keyboards, attachments, file sizes, deep links, webhooks, bots per profile, update/button types, and errors.

Instructions

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotence are covered by structured data. The description adds value by indicating the return shape ('in one table' and 'each with a source link'), which matters since there is no output schema. It does not state whether limits are versioned, cached, or how authoritative the snapshot is.

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 resource identity, then a dense enumerated list of covered topics that each carry information. The long dash list is heavy but every item signals retrievable content rather than filler.

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 lookup tool with a single optional parameter and no output schema, the description does the important work: it enumerates exactly which limit categories can be answered. Return-value explanation is partially supplied ('each with a source link'). The only gap is routing guidance against the sibling reference tools.

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 only one parameter and schema description coverage is 100%, with the schema itself documenting 'en'/'ru', the default ('ru'), and the XONTA_MAX_LANG fallback. The description says nothing about the lang parameter, so baseline 3 applies — the schema carries all parameter meaning.

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 verb-like framing ('All MAX platform limits in one table') and enumerates concrete contents: text length, rate limits, keyboard size, attachments, file sizes, deep link payloads, webhook rules, bots per profile, plus update types, button types, errors. That makes it clearly a limits/reference lookup rather than a builder or validator. It does not explicitly contrast itself with the sibling max_api_reference, so it stops 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 implied by the content list — an agent can infer 'call this when I need to know a platform limit' — but there is no explicit when-to-use statement, no exclusion, and no pointer to the closely related max_api_reference. Nothing misleading, just implicit.

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