Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_st_flash

Destructive

Read, write, and verify STM32 flash memory through an ST-Link probe while keeping artifacts in the selected engagement namespace and using relative paths.

Instructions

Read, write, and verify STM32 flash through an ST-Link probe. 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_st_flash"
  }
}

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

A3.8/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 agent knows this is a risky mutating operation. The description adds the operations (read/write/verify) and namespace context, but does not detail what specifically gets destroyed or required hardware state. That is adequate but not rich beyond annotations.

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 sentences, front-loaded with the core purpose and followed by essential context. No wasted words; every part earns its place.

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?

The description covers purpose and namespace context, and an output schema exists, so return values need not be explained. However, for a destructive hardware tool with 0% parameter coverage, it leaves significant gaps around how to structure the 'arguments' array and what engagement_id represents.

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 the description must compensate, but it only vaguely mentions relative paths for engagement artifacts, which hints at working_directory without explaining it. It gives no meaning for the required 'engagement_id' or 'arguments' array, leaving critical parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Read, write, and verify STM32 flash through an ST-Link probe.' It distinguishes from siblings because no other tool in the list handles STM32 flashing, and the scope 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 Guidelines4/5

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

It gives clear context: 'Runs from the selected engagement namespace; use relative paths for engagement artifacts.' This tells the agent the tool operates within an engagement and how to handle paths. It does not name alternatives or exclusions, but none are apparent among the siblings.

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