Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dbg Add Bp

dbg_add_bp

Set breakpoints at one or more addresses in an IDA Pro instance to control debugging execution. Specify an instance ID when multiple databases are open.

Instructions

Add breakpoint(s) at address(es).

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": {
      "addr": "<addr>"
    },
    "name": "dbg_add_bp"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYesAddress(es) for breakpoint - single or comma-separated
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.5/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 behavioral burden and does not meet it: it does not say whether the debugger must be running, whether the breakpoint persists in the saved database, or whether software vs hardware breakpoints are used. The mutation intent is only implied by 'Add'.

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 front-loaded sentence with no filler, which is good — but here brevity comes from under-specification rather than tight framing of necessary content.

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 debugger-state-dependent mutation tool with no annotations and no output schema, the description omits the session preconditions, what gets created (and whether it can be removed with dbg_delete_bp), and any return information. The schema covers parameters fully, but everything else 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%, so the schema already explains the single-or-comma-separated address form, the timeout, and the critical instance_id multi-database rule. The description's 'address(es)' adds nothing beyond the schema, so the baseline 3 applies.

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

Purpose3/5

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

The verb+resource pairing ('add breakpoint') is clear and, combined with the name, tells an agent this creates a breakpoint at an address while siblings dbg_delete_bp and dbg_enable_bp do something else. However, it is essentially a restatement of the tool name with no further scoping, so it sits at minimum-viable rather than adding distinguishing detail.

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 indication of when this tool should be used versus alternatives, nor of prerequisites such as a debugger being started (dbg_start) or a database being open. An agent must infer the whole workflow from sibling names.

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