Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dbg Start

dbg_start

Starts the debugger on the current input file, defaulting to the platform’s local debugger; specify a debugger module or timeout for remote or time-limited debugging.

Instructions

Start the debugger on the current input file. The local debugger is

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dbg_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in seconds
debuggerNoDebugger module name; default is the local debugger for this platform ('linux'/'win32'/'macos'). Pass e.g. 'gdb' for remote debugging.
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. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / debugger
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Debugger module name; default is the local debugger for this platform ('linux'/'win32'/'macos'). Pass e.g. 'gdb' for remote debugging."
+}
    • 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 burden, yet it discloses nothing about behavior beyond the bare action: not whether an existing session is replaced or errors, whether the call blocks until the debugger attaches, or what happens on attach failure. The sentence fragment at the end suggests missing context about local vs. remote debugger selection.

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

Conciseness2/5

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

The key action is front-loaded, which is good, but the text terminates mid-sentence with 'The local debugger is', making the description structurally incomplete rather than merely short. Brevity here is a defect, not conciseness.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter session-initiator with a fully documented schema and no output schema, the essentials are roughly covered by the schema, but with no annotations and a truncated description, an agent still lacks guidance on session-state preconditions and failure behavior. Adequate at minimum, not complete.

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 schema already explains timeout, debugger module selection (including remote cases like 'gdb'), and the instance_id multi-database rule in more detail than the description. The description adds no parameter meaning beyond the schema, so 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 first sentence gives a specific verb and resource: 'Start the debugger on the current input file,' which is distinguishable from stepping siblings like dbg_step_over or dbg_continue. However, the second sentence is cut off mid-clause ('The local debugger is'), leaving the scope statement unfinished, and there is no explicit differentiation from adjacent session tools.

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 call this versus dbg_run_to, dbg_continue, or dbg_status, nor any prerequisite such as 'must be called before other dbg_* tools.' The verb 'start' only weakly implies it is the session-entry point, and the truncated sentence removes whatever guidance was intended.

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