Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENNoA GitHub token for higher rate limits (optional — works without one at 60 req/hr)

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
repo_overviewB

High-level overview of a GitHub repository.

Returns stars, forks, open issue count, license, topics, language breakdown, and how long ago it was last pushed to.

commit_activityB

Commit activity for a repo over the last N days.

Returns total commits, commits bucketed per ISO week, top authors, and the latest commit.

stale_pull_requestsB

Open pull requests that have been waiting longer than N days.

Useful for spotting review bottlenecks. Sorted oldest first.

contributor_statsC

Top contributors by commit count over the last N days.

recent_releasesC

Most recent releases for a repo, newest first.

issue_backlogC

Open issue backlog grouped by label, with the oldest issues surfaced.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct analytical view (overview, commits, PRs, contributors, releases, issues). Minor overlap exists: commit_activity reports top authors while contributor_stats ranks contributors, and repo_overview includes issue counts while issue_backlog details issues, but descriptions clarify boundaries.

Naming Consistency5/5

All tools use consistent snake_case noun phrases with descriptive, predictable names. No mixing of conventions or vague verbs.

Tool Count5/5

6 tools is well-scoped for a read-only analytics server; each covers a distinct facet of repository insights without redundancy.

Completeness4/5

Covers core repository, commit, PR, contributor, release, and issue insights. Missing more general PR activity/review metrics and issue activity trends, but the surface is sufficient for common insight queries.

Maintenance

ActivityMaintained
ResponsivenessNo issues