Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_gpsmon

Destructive

Inspect a live GPS/GNSS receiver and parse its NMEA output within an engagement namespace, so you can capture position and satellite data from connected hardware using relative artifact paths.

Instructions

Inspect a live GPS/GNSS receiver and its NMEA output. 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_gpsmon"
  }
}

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

C2.9/5.0
Behavior3/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 risk profile is structured data the agent can read directly. The description adds useful context that this touches a live hardware receiver and produces NMEA output, plus the engagement-namespace/path constraint. It does not explain what the destructive risk consists of, whether hardware access requires elevation, or how the CLI arguments affect the receiver.

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 tight sentences with the core purpose front-loaded and the execution constraint second. No filler, though the second sentence is somewhat generic across this tool family.

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

Completeness2/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 described. However, for a hardware-interacting CLI wrapper with an opaque free-form 'arguments' array and zero schema coverage, the description should say what the arguments represent and what preconditions (device present, root, monitor mode) apply; it does neither.

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 mostly fails. It only indirectly hints at working_directory ('use relative paths for engagement artifacts') and engagement_id ('selected engagement namespace'); the critical 'arguments' array — presumably the gpsmon CLI flags/device spec — and 'stdin' are entirely unaddressed.

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: 'Inspect a live GPS/GNSS receiver and its NMEA output', which tells an agent exactly what domain the tool operates on. It does not differentiate itself from any sibling (e.g. the other oc_ radio/hardware tools), 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative for adjacent tasks. The only contextual instruction is about engagement namespace scoping and relative paths, which is execution mechanics rather than tool selection guidance.

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