Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Xrefs To Field

xrefs_to_field

Find cross-references to a struct field by struct and field name, using heuristic name/offset matching or strict type-confirmed access checks to trace field usage.

Instructions

Search struct field references. Heuristic by default (name/offset text

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": {
      "struct_name": "<struct_name>",
      "field_name": "<field_name>"
    },
    "name": "xrefs_to_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return (1..500)
strictNoOnly report type-confirmed accesses (operand typed as the struct)
timeoutNoTimeout in seconds
field_nameYesField name
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.
struct_nameYesStruct name

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.7/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 behavioral burden, but it is truncated mid-sentence ('...name/offset text') and never explains what heuristic matching means, what strict mode changes, or what the results represent. It gives only a faint signal about default behavior and leaves the agent without enough context for a search tool with meaningful false-positive risk.

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

Conciseness2/5

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

The description is only two fragments and is visibly incomplete, ending with an unclosed parenthesis. Brevity is not the issue; the text is under-specified and fails to form a coherent, front-loaded statement of what the tool does.

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?

For a six-parameter xref search with no annotations and no output schema, the description leaves out the heuristic/strict tradeoff, result format, and the crucial instance_id requirement that the schema itself notes. The schema fills many parameter gaps, but the description does not complete the behavioral picture an agent needs.

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 parameters are already documented in structured form. The description adds 'Heuristic by default,' which relates loosely to the strict parameter, but it does not elaborate on the heuristic-vs-strict distinction beyond what the schema already says.

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: 'Search struct field references.' That distinguishes it from generic siblings like xrefs_to and xrefs_from. The trailing fragment weakens it, but the core purpose is clear.

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?

There is no explicit guidance on when to use this instead of xrefs_to or xrefs_from, nor any prerequisites or exclusions. 'Heuristic by default' hints at an alternative mode but does not explain when the strict mode should be chosen.

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