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

Hex-Rays IDA MCP

by zy723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Function profiling query

func_profile
Read-only

Profile binary functions in IDA with summary metrics and optional sampled details, using address or name filters to analyze size, callers, callees, strings, and constants.

Instructions

Profile functions with summary metrics and optional sampled details.

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": {
      "queries": "<queries>"
    },
    "name": "func_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesFunction profiling query (supports name/address filters + pagination)
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.3/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes that this is a safe read operation. The description adds useful behavioral context by noting sampled and optional details, but it does not mention permissions, rate limits, or execution cost.

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 sentence, front-loaded with the core action and scope. It wastes no words and is appropriately sized given that the schema and output schema carry the detailed structure.

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?

Output schema handles return values and 100% schema coverage handles parameters, so the remaining need is usage context. The description omits when to choose func_profile over func_query, lookup_funcs, or analyze_function, leaving a routing gap for this profiling tool.

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%; fields like addr, count, filter, sort_by, include_lists, and instance_id are all documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 is appropriate.

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 'Profile' and resource 'functions' and clarifies that output includes summary metrics plus optional sampled details. It does not differentiate from sibling tools such as func_query, lookup_funcs, or analyze_function, so it earns 4 rather than 5.

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?

Provides no when-to-use guidance, no prerequisites, and no named alternatives. It leaves the agent to infer context from the many sibling tools.

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