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

Hex-Rays IDA MCP

by zy723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List globals with filters and pagination

list_globals
Read-only

List global variables from an IDA database with optional glob filtering and offset/count pagination to inspect symbols in reverse engineering workflows.

Instructions

List globals with optional filtering and offset/count 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": {
      "queries": "<queries>"
    },
    "name": "list_globals"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesList global variables with optional filtering and 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.4/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 that filtering and offset/count pagination are supported, which is useful behavioral context, but it omits auth needs, rate limits, or other operational details.

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?

Single front-loaded sentence with no wasted words. It conveys the core purpose and the filtering/pagination capability immediately.

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?

An output schema exists and parameter descriptions are complete, so the description need not explain return values or parameter details. It is adequate for a simple read-only listing tool, though usage guidance is absent.

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 the schema already documents all parameters including count, filter, offset, and instance_id. The description mentions filtering and pagination but adds no syntax or format meaning beyond the schema.

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 ('List') and resource ('globals'), and notes filtering and pagination. It is clearly distinguishable from siblings like list_funcs and list_databases by resource, but it does not explicitly contrast itself with those siblings.

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 explicit when-to-use guidance, prerequisites, or alternatives. It only describes what the tool returns, not when an agent should choose it over get_global_value or other listing 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