Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_close

Closes a live browser context and releases its Chromium resources, ending the session's real process lifecycle rather than only marking an engagement closed.

Instructions

Close a live browser context and release its Chromium resources. Unlike engagement close, this has real process lifecycle semantics.

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>",
      "session_id": "<session_id>"
    },
    "name": "oc_browser_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
engagement_idYes

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 declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false. The description adds genuine context beyond them by saying Chromium resources are released and real process lifecycle semantics are involved, which hints that in-flight state is lost. It stops short of saying what is destroyed, whether a second call errors given idempotentHint=false, or what permissions are needed.

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 tight sentences, front-loaded with the action. The contrast sentence is short but slightly opaque since "engagement close" is never grounded in a tool or concept an agent can verify.

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?

An output schema exists, so return values need not be explained. However, for a required-2-param teardown tool, the absence of any parameter meaning and of explicit lifecycle preconditions leaves gaps an agent must guess at.

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?

Schema description coverage is 0% and the description says nothing about engagement_id or session_id — no format, no source (from oc_browser_create?), no indication of which one scopes the lookup. With both parameters required and undocumented in the schema, the description was the only place to compensate and it does not.

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?

"Close a live browser context and release its Chromium resources" gives a specific verb plus resource, and the second sentence contrasts it with another close operation. It is clearly distinguishable from the oc_browser_* action/navigate/screenshot siblings, though the referenced "engagement close" is not obviously one of the listed siblings.

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 implies usage (tear down a live browser context, as opposed to a lighter close) but never states when an agent should call this versus oc_browser_list/get or a session-level close. No prerequisites, no precondition that a session must be live, and no explicit exclusion point.

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