Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete Segment

delete_segment

Remove a memory segment from an IDA Pro database by specifying any address inside it; optionally set deletion flags or disable addresses instead of deleting.

Instructions

Delete a memory segment from the IDB.

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": "delete_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoDeletion flags (0=normal, 1=SEGMOD_KILL: disable addresses)
addressYesAny address within the segment to delete (hex string)
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. It says only 'delete' and does not disclose whether the deletion is reversible, whether the IDB must be saved, what happens to contained addresses/functions, or permission requirements. The schema's flags parameter hints at kill-mode behavior, but the description itself adds no behavioral context.

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?

It is a single front-loaded sentence with no wasted words. However, for a destructive operation the brevity becomes under-specification rather than efficient 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?

This is a destructive mutation with no annotations and no output schema. The description does not explain data-loss implications, save requirements, or error conditions, leaving the agent with insufficient context to call it safely.

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 four parameters, including the flags enum and instance_id requirement. The description adds no meaning beyond the schema, which is the expected baseline.

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 ('Delete a memory segment') within the IDB, which clearly distinguishes it from add_segment and other segment tools. It does not explicitly name siblings, but the operation is unambiguous.

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?

No guidance on when to use this versus alternatives like undefine_items or add_segment, and no prerequisites or cautions. The agent is left to infer that this permanently removes a segment.

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