Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_assets_status

Read-onlyIdempotent

Report offline security asset inventory, sizes, counts, and missing required files. Enable deep for content hashes or verify to compare against the build-time manifest.

Instructions

Report every offline asset (nuclei templates, exploitdb, Seclists, wordlists, nmap scripts, hardware rules, CVE index), its size/count, and whether required assets are missing. deep adds content hashes; verify also compares the build-time manifest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oc_assets_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
deepNo
verifyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 safety is fully covered and the bar is lower. The description adds that the tool enumerates assets with sizes/counts and detects missing required assets, and it discloses that deep and verify do extra work, but it doesn't say whether those flags are expensive or slow. That is meaningful but modest added context.

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 sentences, front-loaded with the main action and the asset list, then the flag semantics. Every clause carries information, though the long parenthetical enumeration is dense and could be trimmed without losing much.

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 needn't be described, and annotations cover the safety profile. The description still explains both optional flags and what is reported, leaving only minor gaps such as the cost of deep/verify and what 'missing required assets' triggers.

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 coverage is 0% and the schema only gives bare titles ('Deep', 'Verify'), so the description carries the full burden; it explains deep (content hashes) and verify (build-time manifest comparison). The word 'also' in 'verify also compares' leaves it ambiguous whether verify implies deep, which keeps this from 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 uses a specific verb and resource ('Report every offline asset') and enumerates the asset classes covered (nuclei templates, exploitdb, Seclists, wordlists, nmap scripts, hardware rules, CVE index) plus the missing-asset check. That makes the scope unmistakable, but it never names a sibling such as oc_offline_status, so the agent must infer the boundary 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 description implies usage through the flag semantics ('deep adds content hashes; verify also compares the build-time manifest'), which tells the agent how to escalate detail. It gives no explicit when-to-use or when-not-to-use guidance and no alternatives, so the agent must infer the trigger conditions.

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