Skip to main content
Glama
kunwarVivek

mcp-github-project-manager

get_project_readme

Retrieve README content from GitHub projects to understand project documentation and setup requirements.

Instructions

Get the README content of a GitHub project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • The core handler method that executes a GraphQL query to fetch the README content for the specified GitHub project.
    async getProjectReadme(data: {
      projectId: string;
    }): Promise<{ readme: string }> {
      try {
        const query = `
          query($projectId: ID!) {
            node(id: $projectId) {
              ... on ProjectV2 {
                readme
              }
            }
          }
        `;
    
        interface GetReadmeResponse {
          node: {
            readme: string | null;
          };
        }
    
        const response = await this.factory.graphql<GetReadmeResponse>(query, {
          projectId: data.projectId
        });
    
        return {
          readme: response.node?.readme || ''
        };
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Zod schema definition and ToolDefinition object for input validation, description, and usage examples.
    export const getProjectReadmeTool: ToolDefinition<GetProjectReadmeArgs> = {
      name: "get_project_readme",
      description: "Get the README content of a GitHub project",
      schema: getProjectReadmeSchema as unknown as ToolSchema<GetProjectReadmeArgs>,
      examples: [
        {
          name: "Get project README",
          description: "Retrieve the README for a project",
          args: {
            projectId: "PVT_kwDOLhQ7gc4AOEbH"
          }
        }
      ]
    };
  • Registers the getProjectReadmeTool in the central ToolRegistry singleton instance.
    this.registerTool(getProjectReadmeTool);
  • src/index.ts:274-275 (registration)
    Dispatch handler in main MCP server that routes tool calls to the ProjectManagementService.
    case "get_project_readme":
      return await this.service.getProjectReadme(args);
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 retrieves README content, implying a read-only operation, but does not specify if it requires authentication, rate limits, error handling, or the format of the returned content. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence that directly states the tool's function without unnecessary words. It is front-loaded and efficiently conveys the core purpose, making it easy to parse quickly. There is no wasted language or redundancy.

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 tool's simplicity (1 parameter, no annotations, no output schema), the description is minimal but inadequate. It does not cover parameter meaning, behavioral details like authentication or output format, or usage context compared to siblings. For a tool in a server with many sibling tools, more completeness is needed to guide 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?

The input schema has 1 parameter with 0% description coverage, and the tool description does not mention any parameters. Since there is only one parameter, the baseline score is 4, but the description adds no value beyond the schema, so it is adjusted to 3. It fails to explain what 'projectId' represents or how to obtain it, which is a missed opportunity for clarity.

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: 'Get the README content of a GitHub project.' It specifies the verb ('Get') and resource ('README content of a GitHub project'), making it easy to understand what the tool does. However, it does not differentiate from sibling tools like 'get_project' or 'update_project_readme', which would require more specificity to score a 5.

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 does not mention any prerequisites, such as needing a project ID, or compare it to sibling tools like 'get_project' (which might return general project info) or 'update_project_readme' (for modifying the README). Without such context, users may struggle to select the correct tool.

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/kunwarVivek/mcp-github-project-manager'

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