Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

get_file_contents

Retrieve file or directory contents from GitHub repositories 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
branchNoBranch to get contents from

Implementation Reference

  • Core handler function that fetches file or directory contents from GitHub API, decodes base64 content for files, and returns the data.
    export async function getFileContents(
      owner: string,
      repo: string,
      path: string,
      branch?: string
    ) {
      let url = `https://api.github.com/repos/${owner}/${repo}/contents/${path}`;
      if (branch) {
        url += `?ref=${branch}`;
      }
    
      const response = await githubRequest(url);
      const data = GitHubContentSchema.parse(response);
    
      // If it's a file, decode the content
      if (!Array.isArray(data) && data.content) {
        data.content = Buffer.from(data.content, "base64").toString("utf8");
      }
    
      return data;
    }
  • Zod schema defining the input parameters for the get_file_contents tool.
    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"),
      branch: z.string().optional().describe("Branch to get contents from"),
    });
  • index.ts:83-87 (registration)
    Registration of the get_file_contents tool in the MCP server's listTools response, including 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),
    },
  • MCP tool call handler that validates input arguments using the schema and delegates to the getFileContents implementation, returning JSON stringified response.
    case "get_file_contents": {
      const args = files.GetFileContentsSchema.parse(request.params.arguments);
      const contents = await files.getFileContents(
        args.owner,
        args.repo,
        args.path,
        args.branch
      );
      return {
        content: [{ type: "text", text: JSON.stringify(contents, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get the contents' implies a read operation, it doesn't specify whether this requires authentication, rate limits, what happens with large directories, or the format of returned content. For a tool with 4 parameters and no annotation coverage, this is insufficient.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a straightforward tool and front-loads the essential information.

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 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'contents' means (file content vs metadata), how directories are handled, error conditions, or return format. The description should provide more context given the lack of structured information elsewhere.

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 schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema - it doesn't explain relationships between parameters or provide usage examples. This meets the baseline for high schema coverage.

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. However, it doesn't differentiate from sibling tools like 'search_code' or 'list_commits' that might also retrieve repository content in different ways.

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. There's no mention of when this tool is appropriate versus using 'search_code' for broader searches or 'list_commits' for commit history, nor any prerequisites or constraints for usage.

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/PhialsBasement/mcp-github-server-plus'

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