Skip to main content
Glama

Xonta MAX

max_bridge_mock

Read-only

Generate max-bridge-mock.js: a window.WebApp emulator to develop MAX mini-apps in a normal browser on localhost.

Emulates initData/initDataUnsafe (signed if a test token is given), BackButton (Esc), DeviceStorage and
SecureStorage (localStorage, 10-key cap), BiometricManager, HapticFeedback, NfcManager, ScreenCapture,
requestContact with a valid hash, openLink/downloadFile/shareMaxContent click requirements and per-platform
restrictions. Logs every call. Use only on localhost.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
phoneNo79990000000
user_idNo
platformNoPlatform to emulate: limits which Bridge features workandroid
first_nameNo
entry_pointNodefault
start_paramNoEmulated ?startapp= value
test_bot_tokenNoTEST token: initData and requestContact hash will be validly signed with it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real behavioral detail: signature validity depends on a test token, DeviceStorage/SecureStorage are backed by localStorage with a 10-key cap, BackButton maps to Esc, click requirements and per-platform restrictions apply, and every call is logged. The notable gap is that it never says whether the .js is written to disk or returned as content — material given readOnlyHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The artifact name and its purpose are front-loaded, then the emulated surfaces are packed into a single dense list with no filler. The final 'Use only on localhost' warning is correctly placed at the end as a guardrail.

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 an 8-parameter tool with no output schema and only half the parameters described, the description covers behavior well but leaves the return contract entirely implicit — an agent cannot tell if it gets a file path, a JS string, or a write confirmation. That omission matters for a generator tool with readOnlyHint=true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description compensates for the highest-risk parameters: test_bot_token determines whether initData and requestContact hashes are validly signed, and platform gates which Bridge features work. It adds little for lang, entry_point, or first_name, which remain documented only (or not at all) in the schema.

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 opens with a specific verb and artifact: 'Generate max-bridge-mock.js: a window.WebApp emulator', then enumerates the emulated surfaces (initData, BackButton, DeviceStorage, BiometricManager, NfcManager, etc.). That scope makes it distinguishable from narrower siblings like max_mock_init_data, though it never explicitly names an alternative.

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 context is stated ('to develop MAX mini-apps in a normal browser on localhost') and there is an explicit boundary ('Use only on localhost'), which is genuinely useful. However, there is no guidance on when to pick this versus max_mock_init_data or max_mock_update, and no prerequisites beyond the localhost restriction.

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.