Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_list

Read-onlyIdempotent

Lists live browser sessions owned by this MCP process for a given engagement, helping you verify which scoped automation sessions are available.

Instructions

List live browser sessions owned by this MCP process for one engagement.

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": {
      "engagement_id": "<engagement_id>"
    },
    "name": "oc_browser_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are limited to *live* sessions and to sessions owned by *this* MCP process, not all sessions on the machine. It still omits whether terminated/closed sessions are ever returned, ordering, and any limits on result count.

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 front-loaded sentence with no filler; every qualifier (live, owned by this MCP process, one engagement) constrains the result set and 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?

An output schema exists, so return values need not be described, and annotations cover safety. What remains missing is modest: whether results include session ids/metadata for chaining into other oc_browser_* tools, and handling of an empty or invalid engagement.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is undocumented in the schema (0% coverage), so the description must carry the burden, and the phrase "for one engagement" does map engagement_id to its scoping role. It does not explain the identifier's format or what happens with an unknown engagement id, but for a one-parameter list tool that is a minor gap.

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?

Specific verb plus resource: "List live browser sessions owned by this MCP process for one engagement." The qualifiers "live" and "owned by this MCP process" distinguish it from a general browser-state read such as oc_browser_get or oc_browser_state, though those siblings are not named explicitly.

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?

Usage is implied by the scope constraints (live sessions, only those owned by this MCP process, scoped to a single engagement), which effectively tells the agent when this returns something vs nothing. However, there is no explicit when-to-use guidance, no statement about alternatives like oc_browser_state or oc_browser_get, and no note on prerequisites such as whether the engagement must be active.

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