Skip to main content
Glama

find_references

Locates indexed references tied to one declaration, deliberately excluding unresolved occurrences; provide a repository root and symbol ID to retrieve them.

Instructions

Finds indexed references that resolved to one declaration. Unresolved occurrences are deliberately excluded.

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": {
      "repository_root": "<repository_root>",
      "symbol_id": "<symbol_id>"
    },
    "name": "find_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbol_idYesStable indexed symbol ID returned by outline_file or find_symbol.
repository_rootYesAbsolute path to the Git repository root to explore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: unresolved occurrences are deliberately excluded, so results will be an incomplete reference set. It says nothing about whether the index may be stale, whether the declaration itself is included, what form results take, or any pagination, which are notable gaps for a no-annotation tool.

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

Conciseness5/5

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

Two short sentences with no filler, and the scope-defining statement comes first with the exclusion caveat second. Every word earns its place.

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 two-parameter read tool with fully documented schema and no output schema, the definition covers the essentials and adds the non-obvious exclusion rule. It stops short of describing result shape or index-freshness expectations, which would complete the picture.

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 both parameters are already documented, and the baseline is 3. The phrase 'one declaration' adds a small amount of meaning by clarifying that symbol_id must denote a declaration rather than an arbitrary occurrence, but nothing is added about repository_root or identifier format beyond the schema.

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 ('finds') and resource ('indexed references') with an explicit scope ('resolved to one declaration'). This implicitly separates it from the directional call-graph siblings find_callers/find_callees, but it never names them, so sibling differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: 'resolved to one declaration' signals that the input must be a declaration-level symbol, matching the symbol_id parameter sourced from outline_file/find_symbol. There is no explicit statement of when to prefer this over find_callers, or of any preconditions such as a built index.

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