Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_connection_info

Read-only

Inspect the status of running NexBrowser environments; omit window IDs to list all running windows.

Instructions

Inspect the status of running NexBrowser environments. Omit windowId to list every running window.

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

Input Schema

NameRequiredDescriptionDefault
idsNoAlias of windowId
teamIdNoOptional team filter; OpenAPI uses the active team
windowIdNoOne window ID or a list; omit to list every running window

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2026.11.3
    • changedInput schema / properties / ids / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      }
      -    ]
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / teamId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / teamId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • changedInput schema / properties / windowId / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      }
      -    ]
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
  2. Changed4 schema fields changedv2026.8.20
    • addedInput schema / properties / ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "number"
      +        }
      +      ]
      +    },
      +    {
      +      "items": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "number"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    }
      +  ],
      +  "description": "Alias of windowId"
      +}
    • addedInput schema / properties / teamId / description
      Added value: +"Optional team filter; OpenAPI uses the active team"
    • addedInput schema / properties / windowId / description
      Added value: +"One window ID or a list; omit to list every running window"
    • removedInput schema / required
      Removed value: -[
      -  "teamId",
      -  "windowId"
      -]
  3. Addedv2026.8.14

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe, non-mutating call. The description adds only the windowId-omission behavior (already in the schema) and never says what 'status' actually contains, whether results are cached/live, or how large a listing can get. Minor added value over annotations.

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?

Two short sentences, front-loaded with purpose, with no filler. It could earn a 5 only by spending one of those sentences on sibling differentiation, which it does not.

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 read-only inspection tool with three optional params and no output schema, the agent is left guessing what the returned 'status' object contains and how it differs from nex_browser_list output. Adequate but with a real gap on return-shape expectations and sibling disambiguation.

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 100%, so the schema already explains windowId, ids as its alias, and teamId/active-team behavior. The description's single sentence about omitting windowId merely repeats the schema text and adds nothing about the alias or team scoping. Baseline 3 applies.

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 states a specific verb and resource ('Inspect the status of running NexBrowser environments'), which is clear on its own. However, it never distinguishes this from the sibling nex_browser_list, which an agent could easily confuse with a status-listing call.

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?

The clause 'Omit windowId to list every running window' implies when the bulk-listing form applies, but there is no guidance on when to prefer this over nex_browser_list or when a single-window lookup is appropriate. Usage is only implied, not explicitly routed.

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