Skip to main content
Glama
Sign In
nstbrowser-playwright-mcp

nstbrowser-playwright-mcp

by jackie099
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nst_get_browsers

List running NSTBrowser instances, optionally filtered by status, to see which browsers are starting, running, or stopping.

Instructions

List running NSTBrowser instances

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

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by browser status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral disclosure. 'List' implies a read operation, but the description doesn't disclose that status filtering can return non-running instances, nor does it describe output format or side effects.

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?

A single sentence that is direct and free of unnecessary detail.

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?

The description is minimal and lacks return value details or relationship to sibling tools. For a simple list tool it is usable, but the running/status inconsistency leaves a gap.

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?

The only parameter 'status' is fully described in the schema with enum values. The description adds no extra parameter meaning beyond the phrase 'running', which might be misinterpreted as a fixed state rather than the default filter.

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?

Lists NSTBrowser instances, a distinct resource compared to sessions/profiles. The verb 'List' and resource are clear, but the qualifier 'running' is slightly misleading since the status filter supports starting/stopping as well.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus list_sessions or nst_get_profiles. No alternatives or exclusions are mentioned.

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