Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_captcha_prepare

Prepares a fixed Desktop CAPTCHA bridge from captured widgets and the current online contract; if no ready bridge exists, it guides the agent flow to read the product schema and detect the actual captcha.

Instructions

Free, no purchase: prepare a fixed Desktop CAPTCHA bridge using captured execution capability and the current online contract, without a local product whitelist. Desktop supplies captured widgets and real image grids (for other regular grids pass observed selectors and mode). If no unique ready bridge exists, continue through agentIntegration: read the exact product schema and use nex_captcha_detect with actual productCode/adapter and permitted application tools. Missing fixed capture is not product unavailability; TEXT, CLICK and other enabled products can use the general agent flow. Pass challengeId for multiple widgets. Missing required parameters and schema conflicts must be resolved before charging; never switch to GRID to evade failures or silently reload a filled form. A ready prepareId uses nex_browser_captcha_submit/complete; agentIntegration uses nex_captcha_buy/query and the documented result application.

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": "nex_browser_captcha_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridNo
pageIdNoDefaults to the active page
sessionIdNoDefaults to the active session
challengeIdNo
challengeUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2026.10.24

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior: the operation is free/no purchase, charging is gated behind resolving missing parameters and schema conflicts, and it warns against evading failures by switching to GRID or silently reloading a form. Yet it omits a plain account of what 'prepare' returns and what the prepareId represents.

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

Conciseness2/5

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

The content arrives as one run-on block of semicolon-chained clauses heavy with internal jargon. The core purpose is buried mid-paragraph rather than front-loaded, and several phrases ('current online contract', 'captured execution capability') do not earn their place by clarifying action for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with a nested object, five parameters, no output schema and no annotations, which raises the bar substantially. The description alludes to routing and charging rules but never clearly defines what a prepared bridge/prepareId is or what the agent receives, leaving the definition under-informative for the tool's 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?

Schema coverage is only 40% and two params (challengeId, challengeUrl) have no schema description. The description partially compensates by explaining 'Pass challengeId for multiple widgets' and by noting that other regular grids should pass observed selectors and mode, which gives meaning to the nested grid object. But challengeUrl and the relationship between sessionId/pageId remain unelaborated in prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('prepare') and resource ('a fixed Desktop CAPTCHA bridge'), and adds concrete detail that Desktop supplies captured widgets and real image grids. However, opaque jargon like 'captured execution capability', 'current online contract', and 'local product whitelist' make it hard to state in plain terms what the tool actually produces.

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?

It does route the agent to alternatives: fall back to agentIntegration via nex_captcha_detect when 'no unique ready bridge exists', and use nex_browser_captcha_submit/complete for a ready prepareId versus nex_captcha_buy/query otherwise. But the primary trigger for choosing this tool over nex_captcha_detect is muddled, and the guidance is buried in a dense stream of clauses rather than stated as a clear when-to-use condition.

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

Deploy Server

Other Tools