Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_scan_summary

Read-onlyIdempotent

Summarizes complete OpenCyber tool results while preserving all output, so you can review scan findings without losing raw data.

Instructions

Summarize complete OpenCyber tool results without discarding their output.

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": {
      "results": "<results>"
    },
    "name": "oc_scan_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 fully covered structurally. The description's only additional behavioral claim is that output is not discarded during summarization, which is useful but thin; nothing is said about truncation, size limits, or handling of oversized result sets.

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?

A single well-formed sentence with the key qualifier front-loaded and no filler. It is not padded, though its brevity is partly under-specification rather than economy.

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, and the annotations cover the safety profile. But for a tool whose sole input is an untyped array of arbitrary objects, the definition leaves the agent guessing about the input contract, which is the one thing it must get right to call the 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?

There is a single required parameter, "results", with 0% schema description coverage, so the description carries the full burden of explaining what to pass. It says only "OpenCyber tool results", giving no indication of expected item shape, whether raw tool envelopes or bare payloads are wanted, or whether multiple tools' results can be mixed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ("Summarize") and a resource ("complete OpenCyber tool results"), so the general intent is graspable. However, "complete ... results" is ambiguous phrasing, and it never says what a summary contains or how it differs from simply reading the underlying tool output, so an agent cannot confidently distinguish this from just re-reading results itself.

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 clause "without discarding their output" implies a reason to use it (condensing large outputs while preserving data), which is a real usage signal. But there is no explicit when-to-use, no when-not-to-use, and no mention of which sibling outputs are appropriate inputs, leaving routing decisions to inference.

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