Hex-Rays IDA MCP

Overview Schema Source Related Servers Discussions Admin

Pro runtime health and IDB stats

server_health

Read-only

Check the MCP server and current IDB health/readiness state before reverse engineering tasks, optionally for a specific database instance.

Instructions

Health/ready probe for MCP server and current IDB state.

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

Input Schema

Name	Required	Description	Default
`instance_id`	No	Optional database instance id. If omitted, use the current target.

Output Schema

Name	Required	Description	Default
`module`	No
`status`	No
`busy_sec`	No
`idb_path`	No
`busy_tool`	No
`imagebase`	No
`input_path`	No
`uptime_sec`	No
`queued_calls`	No
`hexrays_ready`	No
`strings_cache_size`	No
`auto_analysis_ready`	No
`strings_cache_ready`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv20261008.0.1Oct 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the description's main added value is scope: it reports both server liveness and current IDB state. It does not disclose whether the probe touches/initializes the database, what 'ready' means, or how instance scoping affects results — modest but real added context over the annotation.

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?

One short sentence with no filler, front-loading the purpose. Nothing could be trimmed without losing information.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the tool is simple (zero required params). The description covers both facets of the probe adequately; only the interaction with instance_id and the meaning of 'ready' remain unstated, which are minor for a health check.

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 single instance_id parameter is fully documented in the schema (optional, defaults to the current target). The description never mentions instance selection, so it adds nothing beyond the schema — 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?

The description names a specific resource ('MCP server' plus 'IDB state') and a clear verb ('Health/ready probe'), so an agent can tell this apart from the analysis-oriented siblings at a glance. It is clear, though it does not explicitly state that no sibling overlaps this function — which is obvious only from the sibling list.

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?

Calling this as a health/readiness probe is strongly implied by the phrasing, but the description gives no explicit 'use this before X' or 'do not use this for Y' guidance. It also does not mention the alternative of list_databases, which also reports IDB information, so the agent must infer the division of labor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server