Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
emu_loadA

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.

emu_runA

Emulate a single function in isolation and return its result.

Use after you have guessed what a function does, to verify the guess against known inputs. args are passed per calling convention (floats go to the floating point argument registers); mem_inputs maps addresses (hex/dec strings) to hex byte data pre-written to memory. Returns return value, main registers, instruction count and stop reason. No syscalls/filesystem/network are emulated; unknown calls stop execution.

emu_traceB

Trace an emulated function: executed addresses and memory read/write summary.

Use to understand control flow or memory access of a function. At most limit addresses are printed per page; use offset to page through long address lists.

emu_read_memB

Read up to 4096 bytes from emulated memory.

fmt is "hex" or "ascii". Use to inspect memory after/before a run.

emu_write_memC

Write hex data to emulated memory. Returns number of bytes written.

emu_hook_callA

Stub a function at addr: skip it and return return_value.

Use for libc/API stubs such as malloc, strlen, printf. Prevents unknown-call stops. A float return_value is returned in the floating point return register. Returns confirmation.

emu_resetA

Reset the emulator session (unload binary, clear hooks and memory).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct action in the emulation lifecycle: load, reset, run, trace, read memory, write memory, and hook a call. The only near-overlap is emu_run vs emu_trace, but their descriptions clearly separate result/register reporting from address-level control-flow tracing. No two tools appear to do the same thing.

Naming Consistency5/5

All seven tools use the same snake_case, emu_-prefixed convention with imperative verb forms (emu_load, emu_run, emu_trace, emu_read_mem). The pattern is predictable throughout, and the read/write pair is symmetric.

Tool Count5/5

Seven tools is a tight, well-scoped set for binary emulation: session setup, execution, introspection, and stubbing. Every tool has an evident role and none feels redundant or tacked on.

Completeness4/5

Load/reset/run/trace/read/write/hook covers the core emulate-and-inspect workflow, including memory inputs and call stubbing. Minor gaps remain: no register write or single-step/breakpoint tool, which could limit fine-grained experimentation, though memory writes and hooks partially work around this.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues