Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_gpspipe

Destructive

Stream GPSD JSON or NMEA data into an engagement artifact from the selected engagement namespace, using relative paths to store output in the engagement.

Instructions

Stream GPSD JSON or NMEA data into an engagement artifact. 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_gpspipe"
  }
}

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/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so the safety profile is carried structurally. The description adds nothing about what is written or overwritten in the artifact, that arbitrary CLI arguments are forwarded, or what happens on failure — the gaps that matter most for a destructive passthrough tool.

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 short sentences with the core action front-loaded and the namespace/path constraint second. No filler, though the terseness comes at the cost of the detail noted in other dimensions.

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, so return-value explanation is not required, and the namespace/path note covers the most confusing parameter. For a destructive tool with four completely undocumented parameters and raw argument passthrough, however, the description is thinner than the complexity warrants.

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?

Schema description coverage is 0%, so all four parameters are undocumented in structured form, and the description compensates only partially by hinting that working-directory paths are relative to the engagement namespace. It says nothing about 'arguments' being forwarded raw to gpspipe, what 'stdin' feeds, or the expected format of engagement_id.

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 — streaming GPSD JSON or NMEA data into an engagement artifact — which is concrete enough for an agent to identify the operation. It does not differentiate itself from any sibling tool, though the surrounding catalog appears to be largely unrelated wrappers, so the gap is modest.

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?

It gives implied usage context (streaming GPS input, running inside an engagement namespace) and one practical instruction about relative paths. There is no explicit when-to-use/when-not guidance and no named alternative for agents that want GPS data handling another way.

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