Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_evaluate

Destructive

Evaluate JavaScript in the active browser page and return a serializable result for scoped inspection, testing, or automation within an engagement.

Instructions

Evaluate JavaScript in the active page and return its serializable result.

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>",
      "expression": "<expression>"
    },
    "name": "oc_browser_evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentNo
expressionYes
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, openWorldHint=true, and idempotentHint=false, so the safety profile is known from structured data. The description adds only that the result must be 'serializable' and that the page must be active — useful but thin context; it never warns that arbitrary code execution can mutate page state or that non-serializable returns will be lost.

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 verb and target appear immediately. It is tight but arguably too terse given the undocumented parameters and destructive behavior.

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 explained, but the definition is still incomplete for a destructive, open-world code-execution tool with 0% parameter documentation. It gives no indication of execution context, error behavior, or how the three required identifiers interact.

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 carries the full burden, yet it explains none of the four parameters. 'expression' and 'argument' are never mentioned, and 'session_id'/'engagement_id' scoping is left entirely implicit, so an agent cannot tell how the optional 'argument' feeds the expression or which session the page belongs to.

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: evaluating JavaScript in the active page. An agent can distinguish this from oc_browser_get, oc_browser_snapshot, or oc_browser_action by the 'evaluate JavaScript' framing, though the description never explicitly names or contrasts those siblings.

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 guidance on when to prefer this over oc_browser_action, oc_browser_get, or oc_browser_snapshot, and no stated preconditions (such as needing an already-created session or a loaded page) or exclusions. The agent must infer usage entirely from 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