Skip to main content
Glama
ddukbg

GitHub Enterprise MCP Server

get-repository

Retrieve repository information from GitHub Enterprise by specifying owner and repository name to access details, manage issues, pull requests, and workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesUser or organization name
repoYesRepository name

Implementation Reference

  • The complete MCP tool registration, schema, and inline handler function for 'get-repository'. It validates inputs, fetches the repository using RepositoryAPI, formats it, handles errors, and returns formatted text response.
    server.tool("get-repository", {
        owner: z.string().describe("저장소 소유자 (사용자 또는 조직)"),
        repo: z.string().describe("저장소 이름")
    }, async ({ owner, repo }) => {
        try {
            // 매개변수 검증
            if (!owner || typeof owner !== 'string' || owner.trim() === '') {
                return {
                    content: [
                        {
                            type: "text",
                            text: "오류: 저장소 소유자(owner)는 필수 항목입니다."
                        }
                    ],
                    isError: true
                };
            }
            if (!repo || typeof repo !== 'string' || repo.trim() === '') {
                return {
                    content: [
                        {
                            type: "text",
                            text: "오류: 저장소 이름(repo)은 필수 항목입니다."
                        }
                    ],
                    isError: true
                };
            }
            const repository = await context.repository.getRepository(owner, repo);
            // 형식화된 저장소 정보
            const formattedRepo = formatRepository(repository);
            return {
                content: [
                    {
                        type: "text",
                        text: `저장소 '${owner}/${repo}' 정보:\n\n${JSON.stringify(formattedRepo, null, 2)}`
                    }
                ]
            };
        }
        catch (error) {
            console.error('저장소 정보 조회 오류:', error);
            return {
                content: [
                    {
                        type: "text",
                        text: `저장소 정보 조회 중 오류가 발생했습니다: ${error.message}`
                    }
                ],
                isError: true
            };
        }
    });
  • Helper function to format raw GitHub repository data into a structured, user-friendly object used by the tool handler.
    function formatRepository(repo) {
        return {
            id: repo.id,
            name: repo.name,
            full_name: repo.full_name,
            private: repo.private,
            description: repo.description || '설명 없음',
            html_url: repo.html_url,
            created_at: repo.created_at,
            updated_at: repo.updated_at,
            pushed_at: repo.pushed_at,
            language: repo.language,
            default_branch: repo.default_branch,
            stargazers_count: repo.stargazers_count,
            forks_count: repo.forks_count,
            watchers_count: repo.watchers_count,
            open_issues_count: repo.open_issues_count,
            license: repo.license ? repo.license.name : null,
            owner: {
                login: repo.owner.login,
                id: repo.owner.id,
                avatar_url: repo.owner.avatar_url,
                html_url: repo.owner.html_url,
                type: repo.owner.type
            }
        };
  • Core API method in RepositoryAPI class that performs the actual GitHub REST API call to retrieve repository details, called by the tool handler.
     * 저장소 세부 정보 조회
     */
    async getRepository(owner, repo) {
        return this.client.get(`repos/${owner}/${repo}`);
    }
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/ddukbg/github-enterprise-mcp'

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