Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_proxy_modify

Update an existing custom proxy resource by sending only the fields that need to change. Credentials remain write-only and are never returned.

Instructions

Update one existing custom proxy resource. Pass only the fields that must change. Credentials are never returned.

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

Input Schema

NameRequiredDescriptionDefault
idNoAlias of proxyId
hostNo
portNoProxy port
remarkNo
proxyIdNoExisting proxy resource ID from nex_proxy_list
passwordNoWrite-only
protocolNoSOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating
usernameNoWrite-only
ipVersionNoIPv4 or IPv6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2026.11.3
    • removedInput schema / properties / id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / id / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / port / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / port / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / proxyId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / proxyId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed4 schema fields changedv2026.10.24
    • changedInput schema / properties / id / description
      Previous value: -"Documented alias of proxyId"New value: +"Alias of proxyId"
    • changedInput schema / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / protocol / description
      Previous value: -"SOCKS5, HTTP, or HTTPS; omitted create defaults to SOCKS5"New value: +"SOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating"
    • changedInput schema / properties / username / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and only partly discharges it. It usefully discloses two behaviors: the update is partial (unmentioned fields are left alone) and credentials are never returned in the response. It omits whether the operation is reversible, what permissions or auth are required, and what happens on an invalid ID, which matters for a mutation tool.

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?

Three short sentences, each carrying distinct information: what it does, how to pass fields, and what is not returned. No filler and no repetition of the schema.

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 a nine-parameter mutation tool with no annotations and no output schema, the definition is adequate but thin. It leaves the identifier requirement, the effect of changing 'protocol' on an existing resource, and failure behavior undocumented, though the 'credentials are never returned' note does cover the most surprising response detail.

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 78%, so the baseline is 3, and the description adds meaning by clarifying partial-update semantics and that username/password are write-only and never echoed back. It does not resolve the more consequential ambiguity: the schema lists zero required parameters while both 'id' and 'proxyId' are described as aliases, so an agent gets no statement that an identifier must be supplied or which of the two to prefer.

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?

States a specific verb and resource: 'Update one existing custom proxy resource.' The word 'existing' plus the singular 'one' implicitly separates it from nex_proxy_create, nex_proxy_batch_create, and nex_proxy_delete. It stops short of naming those siblings explicitly, so it lands just below the top band.

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?

'Pass only the fields that must change' gives real guidance on partial-update semantics, which is the main usage decision for this tool. However, it never says when to use this versus nex_proxy_create, nex_proxy_batch_create, nex_proxy_delete, or nex_proxy_detect, and gives no prerequisites such as needing an existing ID from nex_proxy_list.

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