Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_history

Read-onlyIdempotent

Retrieve the complete persisted request and response history for an engagement HTTP workbench session, restoring prior traffic details for review and audit.

Instructions

Read the complete persisted request/response history for one engagement HTTP workbench session.

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

Input Schema

NameRequiredDescriptionDefault
session_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds only the qualifiers 'complete' and 'persisted', implying a full stored history rather than a live view or a paged subset, but says nothing about ordering, size, or whether results are truncated.

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, front-loaded with the verb and the resource, with every clause carrying scope information. Nothing is redundant or padded.

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?

The presence of an output schema removes the need to describe return values, and for a simple two-param read the description covers the core semantics. However, with 0% parameter coverage and two required identifiers, an agent is left without guidance on how to obtain or format the IDs, which is the main gap for this tool.

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 both required parameters (engagement_id, session_id) are undocumented in the schema. The description only loosely maps the words 'one engagement' and 'session' onto those names; it gives no format, no indication of which tool supplies the IDs, and no statement that both are mandatory.

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 gives a specific verb ('Read') plus a precisely scoped resource ('complete persisted request/response history') and a clear unit of scope ('one engagement HTTP workbench session'). It is distinguishable from live-traffic siblings like oc_http_repeater or oc_http_request, though it never names an alternative 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 beyond the implied 'you have a session and want its history'. No prerequisites are stated (e.g. that the session must already exist, or that oc_http_session_list can supply a session_id), and no sibling is named as an alternative or complement.

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