Skip to main content
Glama
0xjcf
by 0xjcf

get-file

Retrieve specific file content or code segments from a codebase for analysis. Specify file path and optional line ranges to extract relevant portions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative path to the file
startLineNoStarting line number (1-based)
endLineNoEnding line number (1-based)

Implementation Reference

  • Registers the 'get-file' MCP tool with the server, specifying input schema and inline handler function.
    server.tool(
      "get-file",
      {
        path: z.string().describe("Relative path to the file"),
        startLine: z
          .number()
          .optional()
          .describe("Starting line number (1-based)"),
        endLine: z.number().optional().describe("Ending line number (1-based)"),
      },
      async ({ path, startLine, endLine }) => {
        try {
          const filePath = resolve(process.cwd(), path);
    
          if (!existsSync(filePath)) {
            throw new Error(`File not found: ${path}`);
          }
    
          const content = readFileSync(filePath, "utf8");
          const lines = content.split("\n");
    
          let fileContent;
          if (startLine && endLine) {
            // Adjust for 0-based indexing
            const start = Math.max(0, startLine - 1);
            const end = Math.min(lines.length, endLine);
            fileContent = lines.slice(start, end).join("\n");
          } else {
            fileContent = content;
          }
    
          const result = createSuccessResponse(
            {
              path,
              totalLines: lines.length,
              selectedLines:
                startLine && endLine ? { start: startLine, end: endLine } : null,
              content: fileContent,
            },
            "get-file"
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  createErrorResponse(
                    error instanceof Error ? error.message : String(error),
                    "get-file"
                  ),
                  null,
                  2
                ),
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Executes the 'get-file' tool: resolves file path, reads content with fs.readFileSync, extracts line range if specified, formats success/error JSON responses using helpers.
    async ({ path, startLine, endLine }) => {
      try {
        const filePath = resolve(process.cwd(), path);
    
        if (!existsSync(filePath)) {
          throw new Error(`File not found: ${path}`);
        }
    
        const content = readFileSync(filePath, "utf8");
        const lines = content.split("\n");
    
        let fileContent;
        if (startLine && endLine) {
          // Adjust for 0-based indexing
          const start = Math.max(0, startLine - 1);
          const end = Math.min(lines.length, endLine);
          fileContent = lines.slice(start, end).join("\n");
        } else {
          fileContent = content;
        }
    
        const result = createSuccessResponse(
          {
            path,
            totalLines: lines.length,
            selectedLines:
              startLine && endLine ? { start: startLine, end: endLine } : null,
            content: fileContent,
          },
          "get-file"
        );
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                createErrorResponse(
                  error instanceof Error ? error.message : String(error),
                  "get-file"
                ),
                null,
                2
              ),
            },
          ],
          isError: true,
        };
      }
    }
  • Input validation schema using Zod: path (string, required), startLine/endLine (optional numbers for line range).
    {
      path: z.string().describe("Relative path to the file"),
      startLine: z
        .number()
        .optional()
        .describe("Starting line number (1-based)"),
      endLine: z.number().optional().describe("Ending line number (1-based)"),
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/0xjcf/MCP_CodeAnalysis'

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