Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_session_list

Read-onlyIdempotent

List persistent HTTP workbench sessions within a single engagement to review active connections and track scoped HTTP automation state.

Instructions

List persistent HTTP workbench sessions in one engagement.

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": "oc_http_session_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile needs no restatement. The description adds only that sessions are 'persistent' and engagement-scoped; it says nothing about ordering, pagination, or volume limits that would be useful beyond the annotations.

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 no filler or redundancy. It is efficient, though the brevity leaves no room for the scoping and behavioral detail an agent might want.

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 explained, and the annotations cover safety. For a single-parameter list tool this is close to adequate, but the description never clarifies what a 'persistent session' contains or how results are bounded.

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?

There is a single parameter with 0% schema description coverage, so the description must carry meaning. 'In one engagement' does signal that the required engagement_id scopes the listing, but it adds no format or validation detail beyond the schema's own type definition.

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 ('List persistent HTTP workbench sessions') plus an explicit scope ('in one engagement'), which distinguishes it from the singular oc_http_session_get. It does not name the sibling it differs from, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'in one engagement' implies the context in which to call it, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as single-session retrieval. Usage is only implied.

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