Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_session_update

Destructive

Update an HTTP workbench session's scope, headers, cookies, match/replace rules, TLS verification, and redirect behavior to keep requests correctly scoped and configured.

Instructions

Update an HTTP workbench session's scope, headers, cookies, match/replace rules, TLS verification, or 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>",
      "session_id": "<session_id>"
    },
    "name": "oc_http_session_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNo
cookiesNo
session_idYes
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

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the description's remaining job is to explain what is destroyed or replaced. It does not say whether null fields leave existing values untouched or clear them, nor whether supplying 'rules' or 'scope_hosts' replaces the whole collection or appends. For a destructive, non-idempotent mutation that is a meaningful gap.

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 sentence, front-loaded with verb and resource, with the mutable surface listed in a tight parallel structure. No filler, though the list of fields is doing work the schema could do and crowds out behavioral guidance.

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 no explanation. However, a destructive 10-parameter mutation tool with zero schema description coverage needs to explain partial-update semantics and the four unlisted parameters; the description is a field inventory rather than a usable operational contract.

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 10 parameters, so the description must carry the meaning. It names roughly six (scope, headers, cookies, rules, TLS, redirects) but gives no format or semantics for any, and leaves session_id, engagement_id, timeout_seconds and include_subdomains entirely undocumented. It maps names to fields without adding interpretable meaning beyond the schema keys.

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 uses a specific verb ('Update') with a specific resource ('HTTP workbench session') and enumerates the mutable facets: scope, headers, cookies, match/replace rules, TLS verification, redirect behavior. It is immediately clear this is a mutation of an existing session, distinguishing it from oc_http_session_get/list/create by verb alone, though no sibling is named explicitly.

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, no prerequisite stating a session must already exist (created via oc_http_session_create), and no statement about partial vs full update semantics. The agent must infer from the word 'Update' that this operates on an existing session and not on a new one.

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