Skip to main content
Glama

get_file_contents

Retrieve file or directory contents from a GitHub repository by specifying owner, repo, and path parameters.

Instructions

Get the contents of a file or directory from a GitHub repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
pathYesPath to the file or directory
encodedNoWhether to return the content encoded in base64 (default = true)
branchNoBranch to get contents from

Implementation Reference

  • Core handler function that fetches file or directory contents from GitHub repository using the Contents API, optionally decoding base64 content to UTF-8.
    export async function getFileContents(
      { github_pat, owner, repo, path, encoded = false, branch }: z.infer<
        typeof _GetFileContentsSchema
      >,
    ) {
      let url = `https://api.github.com/repos/${owner}/${repo}/contents/${path}`;
      if (branch) {
        url += `?ref=${branch}`;
      }
    
      const response = await githubRequest(github_pat, url);
      const data = GitHubContentSchema.parse(response);
    
      // If it's a file, decode the content?
      if (!Array.isArray(data) && data.content && !encoded) {
        data.content = Buffer.from(data.content, "base64").toString("utf8");
        data.encoding = "utf8";
      }
    
      return data;
    }
  • MCP server dispatch handler for 'get_file_contents' tool: validates input, invokes the core getFileContents function, and formats a user-friendly text response.
          case "get_file_contents": {
            const args = files._GetFileContentsSchema.parse(params.arguments);
            const contents = await files.getFileContents(args);
            let text = '';
            if (Array.isArray(contents)) {
              // this means it's a directory
              text = `Directory Contents:\n${contents.map(c => `- ${c.path} (${c.type}, ${c.type === 'file' ? c.size.toString() + ' bytes' : ''})`).join('\n')}`
            } else {
              // this means it's a singular file
              text = 
    `File Name: ${contents.name}
    File Path: ${contents.path}
    File SHA: ${contents.sha}
    File Size: ${contents.size}
    File URL: ${contents.url}
    File HTML URL: ${contents.html_url}
    File Download URL: ${contents.download_url}
    File Type: ${contents.type}
    File Encoding: ${contents.encoding}
    File Content:
    \`\`\`
    ${contents.content}
    \`\`\`
    `
            }
            return {
              content: [{ type: "text", text }],
            };
          }
  • Zod input schemas for the get_file_contents tool: public schema (GetFileContentsSchema) used in registration and internal schema (_GetFileContentsSchema) with GitHub PAT used in handler.
    export const GetFileContentsSchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      path: z.string().describe("Path to the file or directory"),
      encoded: z.boolean().optional().describe("Whether to return the content encoded in base64 (default = true)"),
      branch: z.string().optional().describe("Branch to get contents from"),
    });
    
    export const _GetFileContentsSchema = GetFileContentsSchema.extend({
      github_pat: z.string().describe("GitHub Personal Access Token"),
    });
  • src/index.ts:94-97 (registration)
    Registration of the 'get_file_contents' tool in the MCP server's listTools response, specifying name, description, and input schema.
      name: "get_file_contents",
      description: "Get the contents of a file or directory from a GitHub repository",
      inputSchema: zodToJsonSchema(files.GetFileContentsSchema),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function without behavioral details. It doesn't disclose whether this is a read-only operation (implied but not explicit), authentication requirements, rate limits, error conditions, or what happens with large files/directories. The description adds minimal value beyond the obvious action.

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 with the core action and resource, making it immediately understandable with zero waste.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks crucial context about authentication, rate limits, return format (especially given the encoded parameter), error handling, and how it differs from sibling tools. The description alone is insufficient for safe and effective use.

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 already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific context beyond what's in the schema (e.g., it doesn't explain path formatting conventions or when to use branch vs default). 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 action ('Get the contents') and resource ('file or directory from a GitHub repository'), making the purpose immediately understandable. It distinguishes from siblings like get_issue or get_gist by specifying file/directory content retrieval, though it doesn't explicitly contrast with similar tools like search_code.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., authentication needs), constraints (e.g., file size limits), or when to choose other tools like search_code for broader queries or get_gist for gist-specific content.

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/MissionSquad/mcp-github'

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