Skip to main content
Glama

Outgoing Calls

outgoing_calls

Analyze Svelte code to identify all functions and methods called by a specific symbol, enabling developers to trace dependencies and understand code flow within their projects.

Instructions

Find all functions/methods called by the specified symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the file
symbolNameYesName of the symbol to find
symbolKindNoKind of symbol

Implementation Reference

  • The handler function for 'outgoing_calls' which attempts to retrieve call hierarchy information from the LSP and formats the result.
      async ({ filePath, symbolName, symbolKind }): Promise<ToolResult> => {
        try {
          const prep = await prepareSymbolRequest(lsp, filePath, symbolName, symbolKind);
          if ("error" in prep) return textResult(prep.error);
    
          // Try native call hierarchy
          try {
            const prepareResult = await lsp.request(
              "textDocument/prepareCallHierarchy",
              makePositionParams(prep.ctx)
            );
            if (Array.isArray(prepareResult) && prepareResult.length > 0) {
              const result = await lsp.request(
                "callHierarchy/outgoingCalls",
                { item: prepareResult[0] }
              );
              if (Array.isArray(result) && result.length > 0) {
                const lines: string[] = [
                  `Found ${result.length} call(s) from '${symbolName}':`,
                  "",
                ];
                for (const call of result) {
                  if (call.to) {
                    lines.push(formatHierarchyItem(call.to));
                  }
                }
                return textResult(lines.join("\n"));
              }
            }
          } catch {
            // call hierarchy not supported
          }
    
          return textResult(
            `No outgoing calls found from '${symbolName}'.`
          );
        } catch (ex) {
          return textResult(formatError(ex));
        }
      }
    );
  • Tool registration for 'outgoing_calls' including input schema definition.
    server.registerTool(
      "outgoing_calls",
      {
        title: "Outgoing Calls",
        description:
          "Find all functions/methods called by the specified symbol.",
        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"),
        }),
      },
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' items, implying a read-only operation, but doesn't clarify aspects like error handling, performance characteristics, or output format. For a tool with no annotations, this is a significant gap in transparency.

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 purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent 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 complexity of code analysis tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., a list of symbols, their locations), error conditions, or how it interacts with sibling tools. This leaves gaps for an agent to use it effectively.

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, so the schema already documents all parameters (filePath, symbolName, symbolKind). The description doesn't add any meaning beyond this, such as explaining relationships between parameters or usage examples. Baseline 3 is appropriate when the 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 tool's purpose: 'Find all functions/methods called by the specified symbol.' It specifies the verb ('find'), resource ('functions/methods'), and target ('specified symbol'). However, it doesn't explicitly differentiate from sibling tools like 'incoming_calls' (which likely finds callers rather than callees), so it misses the highest score.

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. It doesn't mention sibling tools like 'find_references' or 'incoming_calls', nor does it specify prerequisites or contexts for usage. This leaves the agent with minimal direction.

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