Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_ACCESS_TOKENYesYour GitHub personal access token with necessary permissions (repo, workflow, etc.)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
github_get_repositoriesC

獲取 GitHub 倉庫列表

github_get_repositoryB

獲取特定倉庫的詳細資訊

github_get_commitsC

獲取倉庫的提交歷史

github_get_commitC

獲取特定提交的詳細資訊

github_get_workflow_runsC

獲取倉庫的 GitHub Actions 工作流運行

github_get_workflow_runC

獲取特定工作流運行的詳細資訊

github_get_workflow_run_jobsB

獲取工作流運行的任務列表

github_get_job_logsC

獲取工作流任務的日誌

github_get_issuesC

獲取倉庫的問題列表

github_get_issueC

獲取特定問題的詳細資訊

github_create_issueC

創建新問題

github_get_pull_requestsC

獲取 Pull Request 列表

github_get_pull_requestB

獲取特定 Pull Request 的詳細資訊

github_create_pull_requestC

創建新的 Pull Request

github_get_pr_filesC

獲取 Pull Request 的文件變更

github_get_pr_commentsC

獲取 Pull Request 的評論列表

github_create_pr_commentC

在 Pull Request 中發表評論

github_get_issue_commentsC

獲取問題的評論列表

github_create_issue_commentC

在問題中發表評論

github_get_file_contentC

讀取倉庫中的特定文件內容

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 20 tools

Disambiguation4/5

Most tools have clearly distinct resource+action targets, and the singular/plural distinction between list and detail tools (get_issues vs get_issue) is understandable. Minor ambiguity exists between the workflow_run and workflow_runs tools and between job logs and workflow run jobs, but descriptions largely disambiguate.

Naming Consistency4/5

The github_ prefix and verb_noun pattern is applied consistently across most tools, making the surface predictable. However, the set mixes full names and abbreviations for the same resource (get_pull_request vs get_pr_files/get_pr_comments), which is an avoidable inconsistency.

Tool Count4/5

20 tools is on the heavier side but justified by the breadth of the GitHub domain (repos, issues, PRs, commits, workflows, files). Each tool maps to a distinct read or action, so the count stays reasonable rather than bloated.

Completeness3/5

The surface is read-heavy and covers listing/detail/creation for issues and PRs, plus comments, files, and workflow runs. Notable gaps remain: no update or close for issues/PRs, no merge_pull_request, no release/repo creation, and no search, which will cause dead ends for common write workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues