Skip to main content
Glama
Sign In
Hex-Rays IDA MCP

Hex-Rays IDA MCP

by zy723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Function CFG blocks (paginated)

basic_blocks
Read-only

Retrieve control flow graph blocks of a function from a binary, with offset and max_blocks pagination for analyzing function structure.

Instructions

Return function CFG blocks with offset/max_blocks pagination.

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": {
      "addrs": "<addrs>"
    },
    "name": "basic_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrsYesFunction addresses or names to get basic blocks for (e.g. '0x123e', 'main')
offsetNoSkip first N blocks (default: 0)
max_blocksNoMax basic blocks per function (default: 1000, max: 10000)
instance_idNoOptional database instance id. If omitted, use the current target.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv20261008.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the pagination behavior (offset/max_blocks), but does not disclose anything beyond the schema, such as multi-address batching semantics or ordering of returned blocks. With annotations and a full output schema present, a 3 is appropriate.

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 padding; the resource and pagination scope lead immediately. It is efficient, though almost too terse to carry any routing or behavioral context.

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?

With a full input schema, an output schema, and readOnlyHint annotations, the structured data carries most of the burden, and the description is minimally sufficient. It still omits any indication of how this differs from disassembly or function-listing siblings, which is the one contextual gap that matters.

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 each parameter (addrs, offset, max_blocks, instance_id) documented including defaults, max values, and example formats. The description merely restates the pagination parameters, adding no syntax or meaning 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.

Purpose4/5

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

States a specific verb and resource ('Return function CFG blocks') plus the pagination mechanism, so the agent knows exactly what comes back. It does not differentiate from nearby tools like disasm, func_query, or list_funcs, which also surface per-function structural data, leaving sibling selection to inference.

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?

The description gives no when-to-use guidance, no prerequisites, and no named alternative for retrieving control-flow information. An agent must infer that this is the CFG-block tool rather than disasm or func_query based on the name alone.

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