Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dbg Write Mem

dbg_write_mem

Write bytes to specific addresses in a debugged process, enabling direct memory patching and data modification during IDA Pro debugging sessions.

Instructions

Write memory to debugged process.

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": {
      "regions": "<regions>"
    },
    "name": "dbg_write_mem"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionsYesList of {address, bytes: [int,...]}
timeoutNoTimeout in seconds
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.8/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 for a mutating operation. It does not say whether the process must be stopped, whether writes are atomic across regions, what happens on partial failure, or what the tool returns, leaving a destructive-ish write effectively opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with zero waste and the action front-loaded, but it is terse to the point of under-specification given the payload is a structured array of address/bytes pairs.

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?

For a memory-mutating debugger operation with no annotations and no output schema, the description should at least cover return values or session requirements. As written, key operational context is missing.

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% and the region format, timeout, and instance_id disambiguation are all documented in the schema itself. The description adds nothing beyond that, which is the baseline expectation rather than a strength.

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 ('write memory') plus a target ('debugged process'), which cleanly separates it from the sibling dbg_read_mem. It stops short of differentiating it from patch_bytes, patch_asm, or save_database, which all also mutate bytes.

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 prefer this over patch_bytes or dbg_read_mem, and no prerequisites such as needing an active debug session or a paused/suspended target. The agent must infer all of that from the tool name.

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