Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_get

Read-onlyIdempotent

Inspect a live OpenCyber browser session to retrieve its URL, title, network event count, and active interception rules for engagement-scoped troubleshooting and audit.

Instructions

Inspect one live OpenCyber browser session, including URL, title, network event count, and interception rules.

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_get"
  }
}

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that it reports network event count and interception rules; it says nothing about behavior when the session id is unknown or how live state is sampled.

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?

A single front-loaded sentence with no filler; the trailing clause lists returned content rather than padding. Slightly dense but every phrase carries information.

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 little prose, and this is a simple two-parameter read tool. The remaining gap is the unexplained engagement_id scoping and the absence of any mention of failure modes for a non-existent or closed session.

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% for both parameters. The description only loosely hints that session_id selects the single session; engagement_id is never mentioned, so the agent gets no guidance on why both ids are required or how they combine.

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?

Uses a specific verb ("Inspect") and a specific resource ("one live OpenCyber browser session"), and enumerates what the inspection surfaces (URL, title, network event count, interception rules). That distinguishes it from siblings like oc_browser_list and oc_browser_network_log, though no sibling is named.

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?

"Inspect one live ... session" implies the tool is for reading a single existing session by id, which implicitly separates it from the list/create/action variants. However, it never states when to prefer this over oc_browser_state or oc_browser_snapshot, nor any preconditions such as the session being 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