Skip to main content
Glama

Get File References

get_file_references

Find all files that reference or import a specific file in Svelte projects. Use this tool to track dependencies and understand file relationships during development.

Instructions

Find all files that reference/import the specified file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the file

Implementation Reference

  • The tool "get_file_references" is registered and handled within the `registerSvelteTools` function in `src/tools/svelte.ts`. It takes a `filePath` input, converts it to a URI, and makes an LSP request to `$/getFileReferences`.
    server.registerTool(
      "get_file_references",
      {
        title: "Get File References",
        description:
          "Find all files that reference/import the specified file.",
        inputSchema: z.object({
          filePath: z.string().describe("Absolute path to the file"),
        }),
      },
      async ({ filePath }): Promise<ToolResult> => {
        try {
          const uri = pathToUri(filePath);
    
          const result = await lsp.request("$/getFileReferences", uri);
    
          if (!result || !Array.isArray(result) || result.length === 0) {
            return textResult(
              `No references found for ${basename(filePath)}.`
            );
          }
    
          return textResult(formatLocations(result, "file reference"));
        } catch (ex) {
          if (
            String(ex).includes("Unhandled method") ||
            String(ex).includes("not supported")
          ) {
            return textResult(
              "$/getFileReferences is not supported by this version of svelteserver."
            );
          }
          return textResult(formatError(ex));
        }
      }
    );
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 of behavioral disclosure. It states the tool finds references/imports but doesn't cover critical aspects like whether it's read-only, what the output format is, if there are rate limits, or if it requires specific permissions. This leaves significant gaps for a tool that likely interacts with a codebase.

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?

The description is a single, efficient sentence that directly states the tool's function without any fluff or redundant information. It's front-loaded and wastes no words, making it easy to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that likely returns complex data (e.g., a list of file references). It doesn't explain what the output looks like, potential errors, or behavioral traits, leaving the agent with insufficient context to use it effectively in a code analysis workflow.

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?

The input schema has 100% description coverage, with the single parameter 'filePath' clearly documented as an absolute path. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline for adequate but unenriched parameter documentation.

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?

The description clearly states the tool's purpose with a specific verb ('Find') and resource ('files that reference/import the specified file'), making it easy to understand what it does. However, it doesn't explicitly distinguish itself from sibling tools like 'find_references' or 'incoming_calls', which might have overlapping functionality in a code analysis context.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'find_references' and 'incoming_calls' present, there's no indication of how this tool differs or when it's the appropriate choice, leaving the agent to guess based on the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adainrivers/SvelteLS.MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server