Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_screenshot

Destructive

Capture a browser screenshot into a selected engagement and return its relative artifact path to preserve visual evidence for review.

Instructions

Capture a browser screenshot into the selected engagement and return its relative artifact path.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
full_pageNo
session_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the agent knows this is a write. The description usefully explains why: the capture is persisted as an artifact inside the engagement and returns a relative path rather than raw image data. What it does not disclose is what the destruction consists of — whether an existing artifact or a caller-supplied path gets overwritten, or whether repeated captures accumulate artifacts.

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?

One front-loaded sentence with zero filler and the destination scope stated before the return value. It is efficient, though the terseness leaves the behavioral gaps noted above unfilled.

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 re-explained, but the tool still has four parameters at 0% schema coverage and a destructive write profile. For that complexity the single sentence is too thin: an agent cannot tell what 'path' or 'full_page' will do, nor what session state must already exist.

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%, so the description must carry the burden and it largely does not. It implies engagement_id ('selected engagement') and confirms the relative-path return value, but adds nothing about 'path' (a destination override? empty default means auto?) or 'full_page' (defaults to true, with no explanation of the viewport-vs-entire-document tradeoff), and never clarifies how session_id relates to engagement_id.

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?

The description gives a specific verb+resource ('Capture a browser screenshot') and adds the destination scope ('into the selected engagement') plus an output contract ('return its relative artifact path'). It is clear on its own, but it never distinguishes itself from the close siblings oc_browser_snapshot or oc_browser_get, so it stops short of a 5.

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?

There is no when-to-use guidance at all: nothing says when a screenshot is preferable to oc_browser_snapshot, oc_browser_get, or oc_browser_state, and no prerequisites are stated (e.g. that a live session created via oc_browser_create is required). Usage is only implied by the tool name.

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