Skip to main content
Glama

emu_load

Load an ELF, PE, or Mach-O binary with LIEF and map its segments into Unicorn memory before emulating functions. Auto-detects architecture and resets any previous session.

Instructions

Load a binary (ELF/PE/Mach-O) with LIEF and map its segments into Unicorn memory.

Use this first, before emulating any function. Architecture is auto-detected (x86, x64, arm, arm64) unless arch is provided. Resets any previous session.

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

Input Schema

NameRequiredDescriptionDefault
archNo
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose key traits: it mutates state ('Resets any previous session'), depends on LIEF for parsing, and auto-detects architecture unless overridden. It omits failure behavior for unsupported or malformed binaries and any memory-layout or capacity details, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with the action and mechanism, followed by the sequencing rule and the session-reset warning. No filler or redundancy.

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?

An output schema exists, so return values need no explanation, and the description covers the essentials for a stateful loader: ordering, format support, arch override, and session reset. Error conditions and any constraints on what the loaded memory contains are the only notable omissions.

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?

Schema description coverage is 0%, so the description must compensate, and it does for 'arch': it names the accepted values (x86, x64, arm, arm64) and states the auto-detect default when omitted. The 'path' parameter is only implicitly defined via the accepted binary formats rather than explicitly described as the file path, leaving a small gap.

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?

States a specific verb and resource ('Load a binary') plus the concrete mechanism ('LIEF ... map its segments into Unicorn memory') and the accepted formats (ELF/PE/Mach-O). This is clearly distinguishable from siblings like emu_run, emu_trace, or emu_read_mem without opening any schema.

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?

'Use this first, before emulating any function' gives explicit ordering guidance and explains the implied prerequisite relationship to the emulation siblings. It does not name a specific alternative or state when not to call it, which keeps it short of a 5.

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