Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_st_info

Destructive

Probe STM32 devices through an ST-Link debug probe to read chip information and verify target connectivity within an engagement namespace.

Instructions

Probe STM32 devices through an ST-Link debug 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_info"
  }
}

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

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

The annotations state destructiveHint=true and readOnlyHint=false, so the agent already knows this is a mutating operation. The description does not disclose any of the behavioral consequences that matter: what device state or memory could be altered or lost, whether the probe must be exclusively claimed, or what the "arguments" are passed through to. Calling it merely a 'probe' arguably understates the destructive profile the annotations declare, which is a missed opportunity rather than a direct contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the primary purpose, which is good. The second sentence is a useful operational note, but with only two sentences, the space is spent on environment details rather than on the information that is actually missing, such as parameter semantics and destructive consequences.

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 no explanation. For a destructive, non-idempotent hardware-facing tool with an undocumented passthrough argument array, though, the description leaves an agent unable to judge either the invocation contract or the risk. It is not complete enough to call this tool safely and 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. The description only obliquely hints at working_directory and engagement_id through the phrase about relative paths, and it says nothing at all about the required 'arguments' array, which is the main payload and whose contents an agent cannot infer. With zero schema documentation, the description needed to carry this burden and does not.

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

Purpose3/5

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

The first sentence names a specific verb and resource: "Probe STM32 devices through an ST-Link debug probe." However, it never explains what 'info' actually returns or does in relation to the similarly named sibling oc_st_flash, and 'probe' is ambiguous between reading device metadata and issuing an ST-Link command. It is a vague, high-level statement of purpose rather than a differentiated one.

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?

"Runs from the selected engagement namespace; use relative paths for engagement artifacts" gives context about the execution environment, but that is setup guidance rather than when-to-use guidance. There is no statement of when an agent should call this instead of oc_st_flash or any other STM32 tool, and no prerequisites such as requiring the device to be connected or the probe to be accessible.

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