Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_create

Launch an isolated headless Chromium session bound to a specific engagement ID and get back a browser session ID for scoped, auditable web automation.

Instructions

Launch an isolated headless Chromium context inside the OpenCyber container and return a server-generated browser session ID bound to the 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": "<name>"
    },
    "name": "oc_browser_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
user_agentNo
engagement_idYes
extra_headersNo
viewport_widthNo
viewport_heightNo
ignore_https_errorsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds real context beyond them: the browser is isolated and headless, runs inside the OpenCyber container, and the returned session ID is server-generated and engagement-bound. It omits session lifetime, resource limits, whether a close is required (oc_browser_close exists), and auth requirements for the engagement.

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; the resource, the environment, and the return value are all packed in without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but for a 7-parameter creation tool with zero schema coverage the description is too thin: the session lifecycle, the meaning of the browser options, and the TLS-relaxation default are all left for the agent to guess.

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

Parameters2/5

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

Seven parameters with 0% schema description coverage, and the description explains none of them. It gives no meaning for name, user_agent, extra_headers, viewport_width/height, or ignore_https_errors (notably that it defaults to true, which silently weakens TLS verification), and only implies what engagement_id scopes.

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 ('Launch an isolated headless Chromium context') plus the return artifact (server-generated browser session ID bound to the engagement). This clearly separates it from the action/navigate/evaluate siblings that operate on an existing session, though it does not name them.

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 'launch' framing implies this is the prerequisite step before oc_browser_action/oc_browser_navigate/oc_browser_close, but the description never says so explicitly and gives no exclusions, prerequisites, or guidance on how many sessions per engagement.

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