github-triage-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRY_RUN | No | When true, the agent reasons fully but prints WOULD EXECUTE instead of mutating GitHub. Defaults to true. | true |
| GITHUB_TOKEN | Yes | GitHub personal access token used for GitHub API access. | |
| TRIAGE_CONFIG | No | Path to the triage configuration YAML file containing thresholds and per-repo policies. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issueB | Fetch full issue metadata including labels, assignees and comments. |
| search_issuesB | Search issues/PRs in one repository (GitHub search syntax) to find related or duplicate reports. |
| add_labelsA | Add one or more labels to an issue or pull request. |
| post_commentB | Post a comment on an issue or pull request. |
| assign_issueA | Assign one or more GitHub users. Users are verified as assignable first; unverifiable users are rejected, never guessed. |
| close_issueA | Close an issue. DESTRUCTIVE: the first call returns a proposed action for human review and does NOT close anything. Only call again with confirm=true after the human has explicitly approved. |
| get_repository_contextA | Fetch repository decision context: description, topics, README, CONTRIBUTING.md, CODEOWNERS and the available labels. |
| get_pull_requestA | Fetch a pull request with changed files, commits, reviews, CI check status and linked issues. |
| reopen_issueB | Reopen a closed issue. DESTRUCTIVE: requires confirm=true after explicit human approval, same flow as close_issue. |
| get_recent_repository_activityB | List recently updated issues/PRs (default: last 14 days). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action: issue retrieval, PR retrieval, repo context, recent activity, search, labeling, commenting, assigning, closing, and reopening. The retrieval tools have clearly different scopes (specific issue, search results, recent updates), so agents can select correctly without ambiguity.
All tool names use consistent snake_case and follow a predictable verb_noun pattern. Retrieval tools use get_ or search_, while mutation tools use clear action verbs like add_, post_, assign_, close_, and reopen_.
Ten tools is well-scoped for a GitHub triage agent. Each tool covers a focused triage operation, and there is no obvious bloat or redundancy in the set.
The surface covers the core triage lifecycle: reading issues/PRs, searching, labeling, commenting, assigning, closing, reopening, and fetching repository context. Minor gaps remain, such as removing labels, unassigning users, or editing issue/comment content, but agents can work around these for most triage workflows.