Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_shodan

Destructive

Run Shodan CLI commands inside an isolated engagement workspace to enumerate exposed hosts, services, and banners. Supply argv tokens for direct execution without shell parsing.

Instructions

Run shodan from the OpenCyber enumeration toolkit. The container executes shodan directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

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>",
      "arguments": "<arguments>"
    },
    "name": "oc_shodan"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the risk profile is partially covered. The description usefully discloses that argv is passed without shell parsing and that execution is scoped to the engagement namespace, but it omits practical behavior an agent needs: external network calls/API key requirements and what happens to existing artifacts in the working directory.

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?

Three short sentences with the key operational constraint (no shell parsing) front-loaded after the purpose statement. No wasted wording, though the second and third sentences are operationally focused while purpose-critical risk information is absent.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description needn't explain return values. However, for a destructive, open-world external scanner wrapper with four undocumented parameters, it should at minimum note credential/API requirements and the implications of destructiveHint=true.

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?

Schema description coverage is 0%, so the description must carry semantic weight; it partially does by explaining that 'arguments' are raw argv tokens and that paths should be relative to the engagement namespace, implicitly covering engagement_id and working_directory. It never mentions the 'stdin' parameter or format expectations for arguments.

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 names a specific verb and resource ('Run shodan from the OpenCyber enumeration toolkit') and explains how execution happens (direct argv, no shell). It is clear what the tool does, though it does not distinguish its use case from the many other oc_* wrappers beyond the binary name itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives operational hints ('runs from the selected engagement namespace', 'use relative paths for engagement artifacts') but no when-to-use guidance, no prerequisites such as a Shodan API key, and no comparison or routing to alternatives like oc_amass or oc_autorecon.

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