Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_doctor

Read-onlyIdempotent

Checks harness readiness as a pass/warn/fail checklist covering catalog, integrations, assets, wordlists, browser, runtime, hardware, and limits, and returns remediation steps for failures.

Instructions

Report harness readiness as a typed check list: every check has an id, a pass/warn/fail status, a message, and a remediation when it fails. Includes catalog identity alignment, required and optional integrations, assets, wordlists, browser, analysis runtime, hardware domains, and limit environment validity. Read-only and engagement-free.

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

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: it explains the result shape (per-check id, pass/warn/fail, message, remediation) and that no engagement is required, which tells the agent what to expect operationally.

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 outcome and result shape, followed by the coverage list. The domain enumeration is long but functional; it could be trimmed slightly without loss, but there is no filler or repetition.

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 need not be documented, and the annotations cover safety behavior. The description supplies the remaining useful context—what is checked and that no engagement is needed—making it complete for a zero-parameter diagnostic tool.

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?

The tool takes zero parameters, so the baseline is 4. Nothing about inputs needs explaining, and the description does not waste space on phantom parameters.

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 ('Report harness readiness') and enumerates the domains covered (catalog identity, integrations, assets, wordlists, browser, runtime, hardware, limits), so an agent knows exactly what the tool produces. It stops short of naming a sibling or contrasting itself with status-style tools.

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?

'Read-only and engagement-free' implies this is a safe pre-flight check that needs no active engagement context, which helps selection. However, there is no explicit when-to-use statement, no exclusion of alternatives, and no guidance on whether to run it before or after setup steps.

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