Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_session_create

Destructive

Create a persistent, engagement-scoped HTTP session with declared target scope, headers, cookies, TLS and redirect settings for authorized testing.

Instructions

Create a persistent engagement-scoped HTTP workbench session with declared target scope, default headers, cookies, TLS, and redirect behavior.

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>",
      "name": "<name>",
      "base_url": "<base_url>"
    },
    "name": "oc_http_session_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
base_urlYes
verify_tlsNo
scope_hostsNo
engagement_idYes
default_headersNo
timeout_secondsNo
follow_redirectsNo
include_subdomainsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds that the session is persistent and engagement-scoped, but does not explain why creation is flagged destructive, whether re-creating a name overwrites an existing session, or how long persistence lasts. It also promises 'cookies', a capability the schema does not expose, which is a real mismatch between description and structured data.

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, and the key scoping constraints appear early. The only reservation is that the compressed noun-list style trades clarity for brevity without ever defining terms like 'workbench'.

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 described. However, for a destructive, non-idempotent 9-parameter creation tool with zero schema description coverage, a one-sentence description leaves too much undefined for confident invocation.

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% across 9 parameters, so the description must carry the meaning and it largely does not. It generically gestures at scope, headers, TLS, and redirect behavior, but never explains required parameters such as engagement_id, name, or base_url, nor defaults like verify_tls=true, follow_redirects=true, include_subdomains=false, or timeout_seconds.

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 ('Create') and a specific resource ('persistent engagement-scoped HTTP workbench session'), which is enough to distinguish it from siblings like oc_http_session_get/list/update. 'Workbench' is internal jargon that isn't explained, but the resource and scope are identifiable.

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 create a new session versus reusing one, when to use oc_http_session_update instead, or whether an engagement must already exist. The only usage signal is the imperative 'Create'; prerequisites and alternatives are left entirely to inference.

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