Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

nex_browser_connection_info

Read-only

Inspect status of running NexBrowser environments. Specify a window ID for targeted details, or omit it to list all running windows.

Instructions

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

Input Schema

TableJSON 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.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"
-]
  2. Addedv2026.8.14

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'Inspect' verb is consistent with that. The description adds useful context beyond the annotation by scoping to 'running' environments and clarifying the list-all behavior when windowId is omitted. It does not disclose what fields 'status' contains or behavior for invalid/non-running window IDs, but the annotation lowers the burden.

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?

Two sentences with zero waste. The primary purpose is front-loaded in the first sentence, and the second sentence delivers the single most important invocation detail. Every word earns its place.

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?

For a read-only inspection tool with three optional parameters all documented in the schema, the description is largely sufficient. The main gap is the absence of an output schema combined with no description of what 'status' information is returned, which leaves the agent guessing about the response shape. Still, the tool name and description convey the essential semantics.

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 all three parameters (ids, teamId, windowId) are already documented in the schema. The description's 'Omit windowId to list every running window' largely restates the schema's windowId description rather than adding new meaning. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 ('Inspect') and resource ('status of running NexBrowser environments'), making the tool's core function clear. It does not explicitly differentiate from close siblings like nex_browser_list or nex_browser_tab_list, but the 'status of running environments' framing is specific enough to convey what it does.

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 description gives invocation guidance ('Omit windowId to list every running window'), which helps the agent use the tool correctly. However, it provides no when-to-use vs. alternative guidance, no exclusions, and no mention of when a sibling like nex_browser_list would be more appropriate. Usage context is implied rather than explicit.

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

Install Server

Other Tools