Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Trace Data Flow

trace_data_flow

Trace data references—reads, writes, and offsets—to and from a specified address to map cross-references and data flow in reverse engineering.

Instructions

Trace data references (reads/writes/offsets) to and from an address.

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": {
      "address": "<address>"
    },
    "name": "trace_data_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesStart address or symbol name
timeoutNoTimeout in seconds
directionNoto | from | bothboth
max_depthNoMaximum xref hops
max_nodesNoMaximum nodes to include
instance_idNoREQUIRED whenever more than one database is open (from open_database's result or list_databases()); optional only while exactly one instance is live.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedInput schema / properties / instance_id / description
      Previous value: -"Instance id override"New value: +"REQUIRED whenever more than one database is open (from open_database's result or list_databases()); optional only while exactly one instance is live."
  2. First observedv0.9.7

TDQS

C2.9/5.0
Behavior2/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 implies a potentially expensive multi-hop traversal but never says it is read-only, that results can be truncated (max_nodes default 200), that traversal depth is bounded, or that it may be slow enough to need a timeout.

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?

A single front-loaded sentence with zero filler. However, for a six-parameter graph-traversal tool with no annotations, that brevity edges into under-specification rather than tight conciseness.

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?

With no annotations and no output schema, the description should explain the shape of the returned traversal (nodes/edges, hops, truncation behavior) and read-only safety. For a parameterized multi-database traversal tool it leaves too much for the agent to infer.

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?

Schema description coverage is 100%, so the schema already documents all six parameters including direction, max_depth, and instance_id. The description only loosely reinforces 'to and from' versus the direction parameter and adds no syntax, symbol-name handling, or truncation semantics beyond the schema.

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 (trace) and resource (data references: reads/writes/offsets) with scope ('to and from an address'). It is clearer than a tautology, but it does not distinguish itself from overlapping siblings such as xrefs_to, xrefs_from, and xrefs_to_field, which an agent must choose between.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus the multiple xref tools in the sibling set, nor any prerequisite or exclusion. The usage is only inferable from the verb, which is insufficient in a crowded xref-tool cluster.

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

Deploy Server

Other Tools