Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_flashrom

Destructive

Detect, read, write, and verify SPI or parallel flash chips and firmware in an engagement workspace; use relative paths for stored artifacts.

Instructions

Detect, read, write, and verify SPI/parallel flash chips and firmware. 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_flashrom"
  }
}

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
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, and the description's "write" verb is consistent with that profile. It adds useful context about namespace-relative execution, but omits the traits that matter most for a flasher: that writes overwrite target chip contents irreversibly, and that hardware access may be required.

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 short sentences with the capability front-loaded and the environmental constraint trailing. No filler, no repetition of the title, and nothing that could be cut without losing information.

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 explained, but the 0%-coverage argument schema means the caller has no guidance on how to construct the `arguments` argv list or when to use `stdin`. For a destructive, open-world hardware tool with an opaque pass-through interface, the definition leaves too much inference to the agent.

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 must carry the burden and largely does not. The `arguments` array is presumably forwarded to the flashrom CLI, and `stdin` presumably feeds it input, but neither is stated; only `working_directory` is obliquely implied by the relative-path sentence.

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 specific verbs (detect, read, write, verify) and a specific resource (SPI/parallel flash chips and firmware), so the tool's function is immediately clear. It does not, however, distinguish itself from closely related siblings such as oc_avrdude or oc_binwalk, leaving the agent to infer which firmware tool fits a given task.

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?

The only usage steering is operational ("runs from the selected engagement namespace; use relative paths"), which concerns path resolution rather than tool selection. There is no statement of when to prefer this over alternative firmware/ROM tooling, no prerequisites, and no exclusions.

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