Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dbg Thread Regs

dbg_thread_regs

Read registers from one or more debug threads in IDA Pro, temporarily selecting each thread and restoring the prior state afterward.

Instructions

Read registers of one or more debug threads (temporarily selects each thread, then restores).

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_thread_regs"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNoComma-separated register names to read; omit for all registers
timeoutNoTimeout in seconds
thread_idsNoThread ID(s) in decimal (comma-separated ok); omit for all threads
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

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose the key non-obvious trait: each thread is temporarily selected and then restored, which tells the agent about the side effect on debugger state. It stops short of stating that a live debug session is required or what happens for invalid/terminated thread IDs.

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

Conciseness5/5

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

A single front-loaded sentence with the operation stated first and the side-effect caveat in a tight parenthetical. No filler.

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?

Adequate for a 4-param read tool with full schema coverage and no output schema, since return format need not be explained. The remaining gap is sibling routing: the agent gets no explicit rule for choosing between dbg_thread_regs and dbg_regs, nor any stated debugger-session prerequisite.

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%, with names, timeout, thread_ids, and the instance_id multi-database rule all documented in-schema. The description adds no format or default guidance beyond that, so the baseline of 3 applies.

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?

Specific verb+resource ("Read registers of one or more debug threads") with a scope qualifier that implicitly separates it from dbg_regs (current-thread registers). However, it never names dbg_regs, so the agent must infer the distinction from the phrase "one or more debug threads".

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

Usage Guidelines3/5

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

Usage is only implied: the "one or more debug threads" phrasing suggests use when you need registers from threads other than the selected one. There is no explicit when-to-use, no named alternative (dbg_regs), and no stated prerequisite such as an active debug session.

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