Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_http_session_get

Read-onlyIdempotent

Retrieve details for one engagement-scoped HTTP workbench session and its history count to inspect activity or troubleshoot session state.

Instructions

Inspect one engagement-scoped HTTP workbench session and its history count.

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

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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds that the scope is engagement-bound and that a history count is surfaced, which is useful context beyond the annotations, but it says nothing about lookup failure behavior or scoping/permission requirements.

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 front-loaded sentence with zero filler; the verb, scope and resource land immediately. Nothing is redundant with the title or annotations.

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, and the two-parameter surface is simple. Still, with 0% schema description coverage the definition leaves the agent without guidance on how to obtain or format the required IDs, which is the main gap.

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 coverage is 0% – neither engagement_id nor session_id has any description in the input schema, so the description carries the full burden. It only weakly compensates: "engagement-scoped" hints at what engagement_id means and "one ... session" hints at session_id, but no ID format, source, or relationship between the two is given.

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 ("Inspect") and a specific resource ("engagement-scoped HTTP workbench session"), and "one" signals single-item retrieval versus the sibling list tool. The primary noun is somewhat jargon-heavy ("HTTP workbench session"), but an agent can still distinguish it from oc_http_session_list/create/update.

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?

Usage is only implied: the agent can infer this fetches a single session by ID rather than listing or mutating. There is no explicit statement of when to prefer this over oc_http_session_list or oc_http_history, and no mention of prerequisites such as needing a known session_id.

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