Skip to main content
Glama

emu_trace

Trace an emulated function to list executed addresses and summarize memory reads/writes, helping analyze control flow and memory access.

Instructions

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.

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": {
      "func_addr": "<func_addr>"
    },
    "name": "emu_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
limitNo
offsetNo
func_addrYes
max_insnsNo
mem_inputsNo
timeout_msNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the paginated output model ('at most `limit` addresses per page; use `offset` to page'), which is real behavior an agent needs, but omits whether emulation requires a prior emu_load, whether emulator memory/state is mutated, and how timeout or instruction-budget exhaustion manifests.

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?

Three short sentences, front-loaded with the core action and output, then usage, then pagination mechanics. No filler; the only nit is that pagination detail is prioritized over more important undocumented parameters.

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

Completeness2/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-value explanation is rightly omitted, but for a 7-parameter, zero-coverage, annotation-free emulation tool the description is thin: it never covers prerequisites, side effects on emulator state, or the semantics of five parameters.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate, and it explains only `limit` and `offset`. The critical parameters `func_addr`, `args`, `mem_inputs`, `max_insns`, and `timeout_ms` receive no meaning at all, leaving most of the schema opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Trace an emulated function') plus the two artifacts produced (executed addresses, memory read/write summary). It is distinguishable from siblings like emu_run and emu_read_mem by the tracing output, though it never explicitly contrasts with them.

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?

'Use to understand control flow or memory access of a function' gives a genuine usage context, but there are no exclusions or alternative routing (e.g., when to prefer emu_read_mem for raw reads, or emu_run for plain execution). Guidance is implied rather than prescribed.

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