Skip to main content
Glama
Heretek-RE

re-speakeasy

by Heretek-RE

emulate_binary

Emulates a Windows binary (exe/dll) to capture every API call with arguments and return values, returning a structured trace for analysis.

Instructions

Run path under Speakeasy and return a structured per-API trace.

Speakeasy is a Windows API emulator — it loads the .exe / .dll in-process and serves the same Win32 surface that Windows would, but in pure Python. The trace captures every API call the binary makes (CreateFileW, RegOpenKeyExW, NtCreateFile, etc.) with arguments + return values.

Args: path: Windows .exe / .dll to emulate timeout_s: wall-clock budget (default 60s; binaries that loop or call Sleep(INFINITE) can hang the emulator)

Returns::

{"path": "...",
 "trace": [
    {"api": "CreateFileW", "args": [...], "return": "...",
     "timestamp_ns": N, "module": "kernel32"},
    ...
 ],
 "summary": {"api_count": N, "unique_apis": [...],
             "files_accessed": [...], "registry_keys": [...],
             "processes_spawned": [...], "network_calls": [...]}}

On a missing helper, returns {"status": "WARN", "error": "speakeasy-cli not installed", ...} so the agent knows to retry after install.sh.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
timeout_sNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes the in-process loading, the emulator surface, the trace structure, and the error case for missing helper. It does not mention concurrency, memory, or side effects, but is generally transparent.

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 well-structured with a clear summary, explanation of Speakeasy, parameter details, and return format. It is slightly verbose but each sentence serves a purpose.

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

Completeness5/5

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

Given the complexity (2 parameters, no output schema), the description is highly complete. It explains the tool's operation, parameter behavior, return structure with an example, and error handling, leaving no major gaps.

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

Parameters5/5

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

Schema coverage is 0%, so the description must add meaning. It clearly explains 'path' as Windows .exe/.dll to emulate and 'timeout_s' as wall-clock budget with a warning about hanging, providing crucial context beyond the schema.

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 specifies the tool runs a binary under Speakeasy and returns a structured per-API trace. It distinguishes itself from siblings (check_speakeasy, list_emulated_apis) by focusing on execution and trace generation.

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?

The description implies when to use this tool (to emulate a binary and get a trace) and mentions the timeout default and potential hanging, but does not explicitly state when not to use it or compare with siblings.

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-speakeasy'

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