Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_offline_status

Read-onlyIdempotent

Reports airgap posture by verifying offline mode, required asset readiness, local CVE database presence, and which features still require internet access.

Instructions

Report airgap posture: offline mode, required asset readiness, local CVE database presence, and which features still require internet access.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing exactly what the report contains, notably which features still require internet access, which lets an agent plan around airgapped limitations. It stops short of saying whether the check is local-only/fast or how stale the CVE database signal is.

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 front-loaded sentence with a colon-delimited enumeration of the reported checks. No filler, no repetition of the tool name, and the most important framing (airgap posture) comes first.

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?

With an output schema present, return-value detail is unnecessary, and the zero-parameter schema plus rich annotations mean little else must be described. The description covers the scope of the report adequately; only minor context, such as freshness or cost of the check, is absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 would normally apply. However, the description also introduces no semantics for the check categories it names (e.g. what counts as 'required asset readiness'), so it adds no schema-level meaning.

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 gives a specific verb (Report) and resource (airgap posture) and enumerates the four things checked: offline mode, required asset readiness, local CVE database presence, and internet-dependent features. It is clearly a diagnostics/status read, distinguishable from action-oriented siblings such as oc_aircrack or oc_amass, though it never explicitly contrasts itself with oc_assets_status despite overlapping on asset readiness.

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 only implied: an agent can infer it should call this before running tools that need internet or a local CVE DB, but the description never states when to use it, when not to, or which sibling to prefer. No prerequisites or call-ordering guidance are given.

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