Skip to main content
Glama

Xrefs

xrefs
Idempotent

Returns analyzed references to a code or data address so you can trace connections between strings, globals, selectors, and functions. Provide an explicit address for headless providers like Ghidra.

Instructions

Return analyzed references to a code or data address. Hopper may default to its current cursor; headless providers such as Ghidra require an explicit address. Use to connect strings, globals, selectors, and functions; bare addresses are untyped and indirect references may be incomplete. Use inspect_native_instruction at the target address for typed incoming references where supported.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xrefs"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoA provider-normalized address; default memory uses 0x-prefixed hexadecimal
documentNoThe active target's provider document name; use open_binary to switch targets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=false, idempotentHint=true, destructiveHint=false, so the description carries most of the load and does add real context: provider-specific address defaults, that bare addresses are untyped, and that indirect references may be incomplete. Its 'Return' framing reads as a pure read while readOnlyHint is false, though this is a conservative annotation rather than an explicit conflict; the missing piece is any statement about result volume or ordering.

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?

Three compact sentences, front-loaded with the purpose, then provider behavior, then caveats and the sibling hand-off. No filler, though the caveat sentence packs several distinct ideas (typing, indirect references) into one dense clause.

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 no output schema the description should ideally sketch the return shape, but it partially compensates by characterizing reference typing and incompleteness of indirect xrefs. For a two-parameter read tool with full schema coverage, an agent has enough to call it correctly; only the result structure remains implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both params are documented, so the baseline would be 3, but the description adds genuinely new semantics: 'address' is effectively optional under Hopper (cursor fallback) yet mandatory under headless providers, which the schema's zero required params does not convey. That conditional-requirement detail is the kind of meaning the schema cannot express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb and resource ('Return analyzed references to a code or data address') and immediately distinguishes itself from inspect_native_instruction for typed incoming references. An agent can tell what this returns and how it differs from the nearest sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names concrete use cases (connect strings, globals, selectors, functions) and explicitly routes the agent to inspect_native_instruction for typed incoming references where supported. It also spells out the provider-dependent calling condition: Hopper may default to the cursor while headless providers like Ghidra require an explicit address.

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