Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_poc_evidence

Read-onlyIdempotent

List proof-of-concept runs for an engagement with verdicts and evidence paths, or read a specific run's structured result and artifacts by supplying its run_id.

Instructions

List PoC runs in the engagement with verdict and evidence paths, or read one run's structured result and artifacts when run_id is supplied.

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

Input Schema

NameRequiredDescriptionDefault
run_idNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 openWorldHint=false, so the safety profile is fully covered structurally. The description adds useful behavioral context by disclosing what each mode yields (verdict, evidence paths, structured result, artifacts). It stops short of anything like result limits, pagination, or behavior when the engagement has no runs.

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 primary list behavior and trailing the conditional single-run mode. Every clause adds information; nothing is repeated from the name or annotations.

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?

For a two-mode read tool with an output schema, the description covers both usage paths and the salient return contents, so an agent can call it correctly. Minor gaps remain around empty-result behavior and the exact meaning of engagement_id, but these are modest given the rich annotations and output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden — and it does for the decisive one, explaining that run_id selects single-run read versus list mode. engagement_id is only implied through 'in the engagement', and neither parameter's format is specified, which keeps this below a 5.

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 resource (PoC runs in the engagement) and states two distinct operations: listing runs with verdict and evidence paths, or reading a single run's structured result and artifacts. An agent knows exactly what data comes back in each mode. It does not, however, differentiate itself from adjacent tools such as oc_poc_run or oc_evidence_export.

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

Usage Guidelines4/5

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

The mode switch is stated explicitly: omit run_id to list, supply run_id to read one run. That is clear conditional guidance an agent can act on without opening the schema. What is missing is exclusion guidance — it never says when to prefer oc_poc_run or oc_evidence_export instead.

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