Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_angr_analyze

Read-onlyIdempotent

Run angr-based analysis on a workspace binary to inspect program behavior and support reverse engineering or vulnerability triage.

Instructions

Analyze a workspace binary with the angr Python library.

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>",
      "path": "<path>"
    },
    "name": "oc_angr_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
engagement_idYes
auto_load_libsNo

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered without help. The description adds nothing beyond that: it does not disclose that angr analysis is typically long-running and compute-heavy, nor does it mention any timeout or resource considerations.

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?

A single front-loaded sentence with no filler, so nothing is wasted. The problem is under-specification rather than verbosity; brevity here costs more than it saves.

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. But for a three-parameter binary-analysis tool with zero schema coverage and significant runtime cost, the description omits the information an agent needs to invoke it correctly or to judge whether it is the right tool.

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 carry the burden of explaining the parameters, and it explains none of them. In particular it is silent on path (workspace-relative vs absolute), engagement_id scoping, and the effect of auto_load_libs on analysis behavior and runtime.

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 verb+resource pair ("Analyze a workspace binary") is present, and naming the angr library narrows the domain to binary analysis. However, "analyze" is generic and the description never says what angr produces here (symbolic execution, CFG recovery, path exploration), nor is it distinguished from sibling binary tools such as oc_binwalk or oc_firmware_analyze.

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, no prerequisites, and no mention of alternatives. An agent has no way to know whether this belongs in a firmware triage flow versus a general binary inspection flow.

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