Skip to main content
Glama

Find Definition

find_definition

Locate symbol definitions in Svelte files to navigate code structure and understand component relationships during development.

Instructions

Find the definition of a symbol by name in a file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the file
symbolNameYesName of the symbol to find
symbolKindNoKind of symbol: class, method, property, field, interface, enum, function, variable, etc.

Implementation Reference

  • Handler for the "find_definition" tool. It uses prepareSymbolRequest to locate the symbol and then makes an LSP request for "textDocument/definition".
    async ({ filePath, symbolName, symbolKind }): Promise<ToolResult> => {
      try {
        const prep = await prepareSymbolRequest(lsp, filePath, symbolName, symbolKind);
        if ("error" in prep) return textResult(prep.error);
    
        const result = await lsp.request(
          "textDocument/definition",
          makePositionParams(prep.ctx)
        );
        return textResult(formatLocations(result, "definition"));
      } catch (ex) {
        return textResult(formatError(ex));
      }
    }
  • Registration of the "find_definition" tool, including its title, description, and input schema.
    server.registerTool(
      "find_definition",
      {
        title: "Find Definition",
        description: "Find the definition of a symbol by name in a file.",
        inputSchema: z.object({
          filePath: z.string().describe("Absolute path to the file"),
          symbolName: z.string().describe("Name of the symbol to find"),
          symbolKind: z
            .string()
            .optional()
            .describe(
              "Kind of symbol: class, method, property, field, interface, enum, function, variable, etc."
            ),
        }),
      },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but lacks behavioral details: it doesn't specify if it requires a loaded project, what happens if the symbol isn't found, whether it returns a location or full definition, or any error conditions. This is inadequate for a tool with no annotation coverage.

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 with zero waste. It's front-loaded and appropriately sized for the tool's complexity, 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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., definition text, location), behavioral traits like error handling, or how it differs from siblings. For a 3-parameter tool in a code analysis context, this leaves significant gaps.

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 the schema fully documents parameters. The description implies parameters (symbol name and file) but adds no meaning beyond the schema, such as format examples or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb 'find' and resource 'definition of a symbol by name in a file', making the purpose specific and understandable. It doesn't explicitly differentiate from siblings like 'find_references' or 'find_document_symbols', which would require more detail about scope or output differences.

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 siblings like 'find_references' and 'find_workspace_symbols', it's unclear if this is for local file definitions only or how it differs in context. No prerequisites or exclusions are mentioned.

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