Skip to main content
Glama
Heretek-RE

re-angr

by Heretek-RE

symbolic_exec

Run symbolic execution on PE/ELF/MachO binaries starting at a given address to explore program paths and collect constraints, enabling cross-validation of analysis results.

Instructions

Run angr symbolic execution starting at address.

Args: path: PE / ELF / MachO to analyze address: entry point as a hex string (e.g. "0x401000") args: optional list of symbolic-arg names (default: none — angr marks stdin / argv as symbolic depending on the binary's entry point conventions)

Returns::

{"path": "...",
 "address": "0x401000",
 "states_explored": N,
 "constraints": [{"path": [...], "expr": "..."}],
 "dead_ends": N}

The output is a partial trace — angr explores until either all paths are explored or the timeout is hit. The result is useful for cross-validation: "angr and Triton both find this MBA identity holds" is a much stronger signal than either alone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
addressYes
argsNo
Behavior5/5

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

The description fully carries the burden of behavioral disclosure. It explains the tool is a partial trace, explores until timeout or all paths, describes return values, and notes default behavior for args. No annotations exist, so this is comprehensive.

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?

The description is structured as a docstring with clear sections. Every sentence adds value, including purpose, parameter details, return format, and use case. No wasted words.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, parameters, return format, and limitations (partial trace, timeout). It could mention default timeout or how to set it, but is generally complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds significant meaning: path is PE/ELF/MachO, address is hex string, args are optional symbolic-arg names with default behavior explained. It compensates well for the missing schema descriptions.

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 clearly states 'Run angr symbolic execution starting at *address*', specifying the tool and key input. It distinguishes the tool from siblings (build_cfg, check_angr, reaching_definitions) by focusing on symbolic execution and mentioning cross-validation with Triton.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for symbolic execution and cross-validation with Triton, but does not explicitly state when to use this tool over alternatives. No direct comparison or when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Heretek-RE/re-angr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server