Skip to main content
Glama

Xonta MAX

max_mock_init_data

Read-only

Produce a correctly signed MAX mini-app initData string (two-step HMAC with 'WebAppData') for backend tests, with the token used, so you can check your validator end to end.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
user_idNo
chat_typeNoWhere the mini-app was openedDIALOG
first_nameNo
age_secondsNoMake auth_date this many seconds old, to test expiry
start_paramNoValue from ?startapp=
test_bot_tokenNoA TEST token to sign with. Omit to generate a random one. Never pass a production token to a hosted server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower, and the description still adds real behavior: the returned payload includes the token used, and it warns that a production token must never be sent to a hosted server. The signing algorithm detail is also useful context beyond structured fields, though nothing is said about randomness or determinism of generated tokens.

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 front-loaded sentence that puts the produced artifact first and the purpose second. It is slightly dense with the parenthetical scheme note and the trailing 'with the token used' clause, but nothing is superfluous.

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?

With seven optional parameters and no output schema, the description does well to state that the token is returned alongside the string. However, it gives no hint of the returned shape beyond that, and several test-oriented parameters (age_seconds for expiry, start_param) are left entirely to the schema.

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 71%, so the schema carries most of the parameter burden, making 3 the baseline. The description adds the important fact that the signing token is echoed back for validator checks, but it says nothing about age_seconds, start_param, or chat_type semantics beyond what the schema already documents.

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 concrete verb and artifact — 'Produce a correctly signed MAX mini-app initData string' — and even specifies the signing scheme ('two-step HMAC with WebAppData') and domain ('for backend tests'). That is far more specific than a restatement of the name, though it never names a sibling such as max_mock_update to draw a boundary.

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: 'for backend tests' and 'so you can check your validator end to end' tell the agent the scenario, and 'Omit to generate a random one' clarifies one parameter choice in the schema. There is no explicit when-not-to-use guidance or routing to a related sibling for other mock scenarios.

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.