Skip to main content
Glama

fork_repository

Create a copy of a GitHub repository to your account or organization for independent development, testing, or contribution.

Instructions

Fork a GitHub repository to your account or specified organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
organizationNoOptional: organization to fork to (defaults to your personal account)

Implementation Reference

  • The main handler function that performs the GitHub repository fork operation using the GitHub API.
    export async function forkRepository(
      github_pat: string,
      owner: string,
      repo: string,
      organization?: string
    ) {
      const url = organization
        ? `https://api.github.com/repos/${owner}/${repo}/forks?organization=${organization}`
        : `https://api.github.com/repos/${owner}/${repo}/forks`;
    
      const response = await githubRequest(github_pat, url, { method: "POST" });
      return GitHubRepositorySchema.extend({
        parent: GitHubRepositorySchema,
        source: GitHubRepositorySchema,
      }).parse(response);
    }
  • Zod schemas defining the input parameters for the fork_repository tool, including the public schema and internal schema with GitHub PAT.
    export const ForkRepositorySchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      organization: z.string().optional().describe("Optional: organization to fork to (defaults to your personal account)"),
    });
    
    export const _ForkRepositorySchema = ForkRepositorySchema.extend({
      github_pat: z.string().describe("GitHub Personal Access Token"),
    });
  • src/index.ts:113-117 (registration)
    Tool registration in the MCP server's listTools response, defining the name, description, and input schema.
    {
      name: "fork_repository",
      description: "Fork a GitHub repository to your account or specified organization",
      inputSchema: zodToJsonSchema(repository.ForkRepositorySchema),
    },
  • src/index.ts:331-337 (registration)
    Dispatch logic in the MCP server's callTool handler that parses arguments and invokes the forkRepository function.
    case "fork_repository": {
      const args = repository._ForkRepositorySchema.parse(params.arguments);
      const fork = await repository.forkRepository(args.github_pat, args.owner, args.repo, args.organization);
      return {
        content: [{ type: "text", text: JSON.stringify(fork, 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 but only states the basic action. It doesn't disclose behavioral traits like authentication requirements, rate limits, whether it's idempotent, what happens if the repository already exists forked, or what the response includes. For a mutation tool with zero annotation coverage, this is a significant gap.

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 gets straight to the point with zero wasted words. It's appropriately sized for a tool with clear parameters and no complex behavioral nuances to explain.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, permissions needed, or how it differs from similar repository operations. Given the complexity of GitHub API operations, more context would be helpful.

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 three parameters thoroughly. The description adds minimal value by mentioning the default behavior for the 'organization' parameter, but doesn't provide additional context beyond what's in the schema descriptions. 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.

Purpose5/5

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

The description clearly states the specific action ('Fork') and resource ('GitHub repository'), and distinguishes it from siblings by focusing on repository forking rather than other GitHub operations like creating issues, branches, or releases. It's precise and unambiguous.

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 like 'create_repository' or other repository-related tools. It mentions the default behavior (forking to personal account) but doesn't explain scenarios where forking is preferred over cloning or creating new repositories.

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