Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_gpsfake

Destructive

Replay or simulate NMEA GPS data through GPSD to test parsers and spoofing scenarios, using relative paths for engagement artifacts.

Instructions

Replay or simulate NMEA data through GPSD for parser and spoof testing. 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_gpsfake"
  }
}

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.4/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 non-idempotent, so the agent knows this is an unsafe, environment-touching operation. The description adds genuinely useful behavior beyond that: it executes inside the engagement namespace and expects relative artifact paths. It does not disclose what is actually put at risk (e.g. an existing gpsd instance or device state) or that arbitrary CLI arguments are passed through.

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?

Two tight sentences, front-loaded with what the tool does and followed by the execution-context caveat. Nothing is padded or redundant.

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?

For a thin CLI-wrapper tool the description covers what it does, where it executes, and how to reference files, and an output schema exists so return values need no explanation. The remaining gap is the argument-vector convention, which an agent must know to invoke it correctly.

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% across four parameters, so the description carries the full burden and largely fails: it never explains that 'arguments' is a raw CLI argument vector, nor what 'stdin' feeds, nor that 'working_directory' is what the relative-path advice refers to. Only the namespace/relative-path sentence indirectly gestures at working_directory and 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?

States a specific verb pairing ('Replay or simulate') with a concrete resource ('NMEA data through GPSD') and names the use case (parser and spoof testing), which is distinguishable from the surrounding recon/cracking siblings. It stops short of contrasting with any named alternative, but the purpose itself is unambiguous.

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 gives a context ('parser and spoof testing') and an operational constraint ('Runs from the selected engagement namespace; use relative paths for engagement artifacts'), which implies when the tool applies. It offers no explicit when-not guidance, no prerequisites (e.g. GPSD must be running), and no pointer to alternatives for live-device GPS work.

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