Skip to main content
Glama
Heretek-RE

re-angr

by Heretek-RE

reaching_definitions

Compute the reaching-definitions graph for a binary function to reveal def-use relationships, showing where each variable was defined and which definitions reach each instruction.

Instructions

Compute the reaching-definitions graph for function.

A reaching definition is "where was the value used at instruction X defined?" angr computes the dataflow analysis statically. The output is a def-use graph: every variable gets a list of definitions; every instruction that reads a variable gets the list of definitions that may reach it.

Useful for the re-mba-deobfuscate skill: the MBA identity x + y == (x & y) + (x | y) looks like arithmetic, but the reaching-defs graph reveals that (x & y) and (x | y) were both defined from the same source — the identity is a no-op substitution.

Args: path: PE / ELF / MachO function: function name (e.g. "main")

Returns::

{"path": "...", "function": "...",
 "defs": [{"variable": "...", "defined_at": "0x..."}],
 "uses": [{"at": "0x...", "reads": ["var1", "var2"]}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
functionYes
Behavior3/5

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

With no annotations, the description carries full burden. It states the analysis is done statically and describes the output as a def-use graph. However, it does not disclose error handling (e.g., missing function) or performance implications. The return structure is outlined but side effects are not mentioned.

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

Conciseness4/5

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

The description is front-loaded with the main purpose and includes an example usage. It is structured with paragraphs, args, and returns. A bit verbose but each sentence adds value.

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?

Given no output schema, the description provides an expected return format. However, it lacks details on error cases, limitations (e.g., large functions), or prerequisites. For a non-trivial analysis tool, more completeness would be beneficial.

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

Parameters3/5

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

The schema has 0% description coverage, so the description adds essential meaning: 'path: PE / ELF / MachO' and 'function: function name (e.g., "main")'. While helpful, it does not specify constraints like file format validation or path requirements.

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 'Compute the reaching-definitions graph for *function*' and explains what reaching definitions are with a concrete example for the re-mba-deobfuscate skill. It distinguishes itself from sibling tools like build_cfg and symbolic_exec by focusing on dataflow analysis.

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 mentions it is 'Useful for the re-mba-deobfuscate skill' but does not explicitly specify when to use or not use this tool versus alternatives. No exclusions or comparisons to siblings are 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