Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_snapshot

Read-onlyIdempotent

Capture current page text and an accessibility-oriented ARIA snapshot, with optional complete HTML, to inspect browser state during authorized security testing.

Instructions

Return the current page text and accessibility-oriented ARIA snapshot, with optional complete HTML.

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

Input Schema

NameRequiredDescriptionDefault
session_idYes
include_htmlNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the useful detail that output is text plus an ARIA accessibility tree rather than raw DOM, but says nothing about output size, whether hidden elements are included, or any truncation behavior for large pages.

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 sentence with zero filler, front-loading the primary return value and appending the optional flag. Every clause 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 structure need not be restated, and the description correctly focuses on what the payload conceptually is. The remaining gap is routing guidance versus sibling read tools, which keeps it short of full completeness.

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

Parameters3/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 load. "With optional complete HTML" usefully explains include_html and matches its default of false, but engagement_id and session_id receive no semantic explanation at all — their scoping role must be guessed from the names.

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 ("Return") and concrete resources: the current page text, an accessibility-oriented ARIA snapshot, and optionally complete HTML. This is enough to distinguish it from a screenshot or network-log tool, but it never names a sibling or explicitly contrasts itself with oc_browser_get or oc_browser_screenshot.

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 explicit when-to-use or when-not-to-use guidance. "Current page" weakly implies it should be called after navigation, but the agent is left to infer whether to prefer this over oc_browser_get, oc_browser_evaluate, or oc_browser_screenshot when inspecting a page.

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