Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_finding_report

Destructive

Writes structured Markdown security findings in an engagement workspace and cites retained evidence IDs with digests and retention state for verifiable reports.

Instructions

Write a structured Markdown security finding inside the engagement workspace. Pass evidence_ids to cite retained tool results by their evidence digest; each is resolved and rendered with its digest and retention state.

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>",
      "path": "<path>",
      "title": "<title>",
      "target": "<target>",
      "severity": "<severity>",
      "summary": "<summary>",
      "evidence": "<evidence>"
    },
    "name": "oc_finding_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
titleYes
targetYes
summaryYes
evidenceYes
severityYes
remediationNo
evidence_idsNo
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 destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavior about evidence_ids being resolved and rendered with digest and retention state, but it never warns that writing to 'path' may overwrite an existing finding, which is the key destructive consequence.

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?

Two tight sentences, front-loaded with the action and followed by the one non-obvious parameter behavior. No filler, though the second sentence could be folded in more cleanly.

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

Completeness2/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 no explanation, but for a 9-parameter destructive write tool with zero schema coverage, explaining a single parameter leaves the agent without enough to fill required fields like path, severity or target correctly.

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% across 9 parameters, so the description must compensate and it largely does not. Only evidence_ids is explained; path, title, target, severity, summary, evidence, remediation and engagement_id are left entirely to bare schema titles, and the distinction between 'evidence' and 'evidence_ids' is only half clarified.

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: 'Write a structured Markdown security finding inside the engagement workspace.' That clearly separates it from the recon/exploitation siblings, though it never names an alternative reporting tool.

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 'inside the engagement workspace' implies the context in which to use it, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g. an existing engagement), and no routing to alternatives.

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