Skip to main content
Glama

Find Xrefs To Name

find_xrefs_to_name
Idempotent

Resolve an exact symbol name against the bound provider's inventory to find cross-references and return address-only projections, with a stable name_not_found result when unresolved.

Instructions

Resolve an exact name against the bound provider's name inventory and return a resolved or unresolved result. Unresolved names use the stable name_not_found reason; this xref workflow returns address-only projections.

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": "malloc"
    },
    "name": "find_xrefs_to_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact name used by this operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations declare idempotentHint=true, destructiveHint=false, and notably readOnlyHint=false, so the safety profile is already partially supplied. The description does add useful behavior beyond that: unresolved names produce a stable 'name_not_found' reason and results are address-only projections. It does not explain why a pure lookup is flagged non-read-only or what the returned addresses represent, leaving a meaningful gap.

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?

Two sentences with no filler, and the core action is front-loaded. The second sentence is dense with internal jargon ('xref workflow', 'address-only projections') that slightly costs first-read clarity but the text is not padded.

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?

For a single-parameter lookup with no output schema, the description should say what comes back (how many addresses, what they point to) and what the unresolved case looks like beyond the reason string. It covers error semantics but leaves the successful return shape underspecified.

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?

With one required parameter at 100% schema description coverage, the schema already documents 'name'. The description does add the important constraint that matching is exact against the provider's inventory, which is genuine semantic value, but nothing about case sensitivity or formatting conventions is offered.

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

Purpose3/5

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

The description states a specific action (resolve an exact name against the bound provider's name inventory) but never plainly says it returns the cross-references pointing at that name; the xref output is only hinted at through the jargon phrase 'address-only projections.' It also gives no differentiation from nearby siblings such as 'xrefs' or 'address_name', so the agent must guess which one actually performs the lookup.

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 when-to-use guidance, no prerequisites (what a 'bound provider' is or how it gets bound), and no exclusions pointing to alternatives like 'xrefs' or 'address_name'. The agent is left to infer selection from the tool name alone.

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