Skip to main content
Glama

exact_references

Read-onlyIdempotent

Find who calls or references a symbol, disambiguate same-named symbols in TS/JS, and get labeled calls/imports with per-file totals and warnings before applying limits.

Instructions

Find who calls or references a symbol. TS/JS compiler bindings exclude same-named unrelated symbols; results label calls/imports and give per-file call totals before limits. Check scope, ambiguity and warnings. Python is heuristic; imported SCIP freshness is unverified.

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": {
      "symbol_name": "<symbol_name>"
    },
    "name": "exact_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoDefinition file; omit to infer.
lineNo1-based symbol line. Omit to infer a declaration; when several match, the response warns about the chosen candidate. Pass file and line to disambiguate.
rootNoAbsolute project root. Omit only where this session started; required elsewhere and on every subagent call.
limitNoShown occurrences; default 100.
formatNoDefault text.
symbol_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / root / description
      Previous value: -"Absolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call."New value: +"Absolute project root. Omit only where this session started; required elsewhere and on every subagent call."
  2. First observedv1.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: language-dependent precision (compiler bindings for TS/JS, heuristic for Python), staleness of imported SCIP data, that results label calls vs imports, and that truncation happens after per-file totals. It does not discuss permissions, project-size limits, or failure modes when no definition is found.

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?

Front-loaded with the core purpose in the first sentence, followed by precision and caveat notes in a compact, dense style. Sentences are telegraphic ('Check scope, ambiguity and warnings') but every one carries information; nothing is redundant.

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?

For a six-parameter, read-only analysis tool with no output schema, the description covers precision characteristics, result labelling, truncation behavior, and a data-freshness caveat, which is what an agent needs to trust and interpret the output. It lacks explicit routing guidance against the sibling reference/blast-radius tools, which is the main remaining gap.

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?

With 83% schema coverage the baseline is 3, and the description adds meaning on top: 'per-file call totals before limits' clarifies how the limit parameter is applied to results, and 'warnings' on ambiguity links to the line-inference behavior documented in the schema. It does not explain the root-requirement or format trade-offs, which remain schema-only.

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: 'Find who calls or references a symbol.' That is unambiguous and an agent can distinguish it from grep/search-style siblings by the call-reference framing. It stops short of naming a contrasting sibling (e.g. blast_radius or grep), so it does not earn a 5.

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

Usage Guidelines4/5

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

'Check scope, ambiguity and warnings' plus the note that TS/JS bindings exclude same-named unrelated symbols tells the agent when this tool is the right, precise choice over text search. There are no explicit exclusions ('do not use for X, use Y instead'), so it lands at 4 rather than 5.

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