contribution-compass
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token used for API requests and data collection. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_project_updatesC | Search important collected updates, ranked only from factual engagement and labels. |
| find_contribution_opportunitiesA | Find open, unassigned contribution leads with reasons, caveats, and evidence URLs. |
| get_project_newsB | Get releases, public roadmap items, and separately labeled HN discussions. |
| get_project_contextC | Get project metadata plus bounded important Signals and recent Observation Events. |
| get_signal_timelineA | Get the append-only discovery/change trail for a stable Signal ID. |
| list_monitored_projectsC | List configured projects with context and collected evidence counts. |
| compare_projectsB | Compare factual project context and Leads observed in the latest snapshot. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog_index | Latest dates and monitored projects available to this server. |
| latest_opportunities | Latest evidence-qualified contribution leads. |
| latest_news | Latest project news and separately labeled HN community discussions. |
TDQS
Scored across 7 tools
Most tools target clearly separate concerns: searching updates, finding opportunities, fetching news, getting context, tracing signal timelines, listing projects, and comparing projects. However, search_project_updates, get_project_news, and get_project_context all operate in the same general 'project information' space and could be confused without careful reading.
All tool names follow a consistent snake_case verb_noun pattern using simple, predictable verbs: search, find, get, list, compare. There are no mixed conventions or vague names.
Seven tools is a well-scoped count for a contribution-monitoring server. Each tool covers a meaningful part of the workflow without excessive redundancy or missing core functionality.
The surface covers exploration, search, discovery of contribution leads, historical signal tracking, and project comparison. The main gap is the lack of tools to manage monitored projects or act on opportunities, but those may be intentionally outside the server's read-only compass role.