Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Find Instructions

find_instructions

Search IDA Pro disassembly for instructions by mnemonic and/or regex pattern, returning limited matches to support targeted reverse engineering analysis.

Instructions

Find instructions by mnemonic and/or a regex over the instruction text.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return
patternNoOptional regex matched against the full instruction text
timeoutNoTimeout in seconds
mnemonicNoMnemonic filter (case-insensitive substring, e.g. 'call'); empty matches all
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.6/5.0
Behavior2/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 says nothing about cost of regex scanning, default limit of 100 or truncation behavior, timeout handling, or the multi-instance requirement. An agent learns only the matching surface, not the operational characteristics of a potentially expensive search.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the matching axes come first. It is perhaps too terse rather than bloated, but nothing in it is wasted.

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?

Five parameters, no annotations, and no output schema: the description never indicates what a hit looks like (address, mnemonic, text?) or whether results are paginated or ordered. For a search tool whose return shape is undocumented elsewhere, this leaves a substantial gap.

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 every parameter is already documented in-schema. The description only echoes mnemonic and regex filtering and adds no format, syntax, or precedence detail 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 description names a specific verb (find) and resource (instructions) and the two matching axes (mnemonic, regex). However, it does not distinguish this tool from close siblings such as find_regex, search_text, or find_bytes, so an agent cannot tell from the description which search surface applies.

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?

It states what can be filtered but gives no guidance on when to use this instead of find_regex or search_text, and no exclusions or prerequisites. The one crucial call prerequisite — needing instance_id when multiple databases are open — appears only in the schema, not the description.

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