Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_result_list

Read-onlyIdempotent

Lists retained tool results for an engagement, newest last, showing total/offset coverage and active retention mode; filter by exact tool name.

Instructions

List retained tool results in the engagement, newest last, with total/offset coverage and the active retention mode. Filter by exact tool name.

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

Input Schema

NameRequiredDescriptionDefault
toolNo
limitNo
offsetNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description adds real value on top: result ordering is 'newest last', the response reports total/offset coverage, and the active retention mode is surfaced. That last detail is important context the annotations do not convey, since results are retained rather than live.

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?

Two tight sentences with no filler; scope, ordering, and coverage are front-loaded before the filtering note. Every clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 spelled out, and the annotations establish the safety profile. The remaining gap is the thin parameter documentation, but for a four-parameter read-only list tool the description is nearly sufficient to call it correctly.

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?

Schema description coverage is 0%, so the description has to carry parameter meaning on its own. It clarifies that 'tool' is an exact-match filter (not a substring search) and that total/offset coverage exists, which implies offset/limit paging, but 'limit' and 'engagement_id' are only obliquely covered and no defaults or bounds are restated.

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 names a specific verb and resource ('List retained tool results') plus the scope ('in the engagement'), ordering ('newest last'), and result metadata ('total/offset coverage and the active retention mode'). It contrasts implicitly with the singular oc_result_get via 'List', but never names that sibling, so the differentiation is left to inference.

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 implied rather than stated: 'Filter by exact tool name' tells the agent how to narrow, and the offset/limit framing implies paging through a large set. There is no explicit when-to-use versus oc_result_get or when-not guidance, so the agent must infer that a single-result fetch belongs elsewhere.

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