Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_captcha_product_schema

Read-only

Reads the adapter schema, example, integration/result contract, and workflow guide for one productCode to clarify the required product integration and result handling.

Instructions

Free, read-only: read the online adapter schema, example, integration/result contract and workflowGuide for one exact productCode. These define product integration; fixed browser adapters are optional shortcuts, not a product whitelist. Keep all schema constraints; examples are placeholders. For any documented enabled product, use nex_captcha_detect with actual productCode/adapter and a confirmed permitted application path, then buy/query and apply the documented result using browser tools. Text may use fill_form, coordinates may use mouse_click_xy with image origin/scale conversion; the token script helper is optional. HTTP_SUBMIT needs a separate site HTTP integration. DOCUMENTATION_REQUIRED blocks paid tasks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productCode": "<productCode>"
    },
    "name": "nex_captcha_product_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
productCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2026.10.24

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and the description is consistent with that ('Free, read-only'). It adds real operational context beyond the annotations: examples are placeholders, schema constraints must be preserved, fixed browser adapters are optional shortcuts rather than a product whitelist, and HTTP_SUBMIT requires a separate site HTTP integration.

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

Conciseness3/5

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

The first clause front-loads the core action well, but the rest is a dense run-on mixing integration workflow, browser tool hints, and payment-gating notes. Much of the downstream guidance (fill_form, mouse_click_xy, token script helper) belongs to other tools and dilutes focus on this read-only lookup.

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?

With no output schema, the description carries the burden of describing what comes back, and it does so by enumerating schema, example, integration/result contract, and workflowGuide. For a single-parameter read-only documentation tool this is sufficient, though it omits any note on output size or how large the workflowGuide may be.

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 0%, so the schema provides only the parameter name 'productCode' with no documentation. The description adds the meaningful qualifier that it must be one exact product code, but it does not state the expected format, casing, or where valid codes come from (presumably nex_captcha_product_list).

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

Purpose5/5

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

States a specific verb and resource: read the online adapter schema, example, integration/result contract and workflowGuide for one exact productCode. Naming 'one exact productCode' separates it from the sibling list tool nex_captcha_product_list, and the returned artifacts are enumerated concretely.

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

Usage Guidelines4/5

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

Gives a clear downstream sequence: for a documented enabled product, use nex_captcha_detect with the actual productCode/adapter, then buy/query and apply the result with browser tools, plus the note that DOCUMENTATION_REQUIRED blocks paid tasks. It does not explicitly state when this tool should be skipped (e.g., cached or already-known schema), which keeps it from a 5.

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