ih8sn1ff

by ih8w1nd

Overview Schema Source Related Servers Discussions Admin

Python

Local

xrefs

Find absolute-immediate references to a value or string in binaries to trace constants and locate related code.

Instructions

Find absolute-immediate references to a value or string.

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": {
      "path": "<path>"
    },
    "name": "xrefs"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`limit`	No
`string`	No
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 19, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Find' implies a read-only query, but the description does not disclose result format, pagination, safety guarantees, or the effect of the limit parameter.

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

Conciseness3/5

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

A single front-loaded sentence with no wasted words. However, for a four-parameter tool with no annotations it is arguably under-specified rather than optimally concise.

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?

With no annotations, no output schema, and 0% parameter description coverage, the one-sentence description leaves the agent without enough context to correctly invoke the tool. It omits path usage, limit behavior, and target/string semantics.

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

Parameters2/5

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

Schema description coverage is 0% for four parameters. The phrase 'to a value or string' loosely maps to the target and string parameters, but path and limit are never mentioned and the distinction between target and string is not clarified.

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 (Find) and resource (absolute-immediate references) and restricts scope to a value or string. The qualifier 'absolute-immediate' implicitly distinguishes this from the sibling xrefs_rip, but no sibling is named explicitly.

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?

Provides no guidance on when to use this tool versus alternatives such as xrefs_rip, disasm, or callgraph. There are no exclusions, prerequisites, or context cues.

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