contribution-compass

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.3.0
Disambiguation5/5
Each tool targets a distinct aspect: searching updates, retrieving project context, finding opportunities, examining signal timelines, and listing projects. There is no overlap in their purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: search_project_updates, get_project_context, find_contribution_opportunities, get_signal_timeline, list_monitored_projects.
Tool Count5/5
With five tools, the set is well-scoped for a contribution intelligence server. Each tool serves a clear need without redundancy or bloat.
Completeness4/5
The read-only surface is solid: searching, contextualizing, discovering opportunities, and tracking signals. The only minor gap is a lack of any action-oriented tools (e.g., claiming or updating contributions), but this fits a compass/insight role.
Average 3.2/5 across 5 of 5 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- No commit activity data available
- Last stable release on August 14, 2026
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It adds that results are 'ranked only from factual engagement and labels,' which is useful context, but it does not disclose side effects (e.g., whether it's read-only), auth requirements, rate limits, or what happens with no matches—leaving significant behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loaded with the primary action. It avoids unnecessary words, but its brevity borders on under-specification—still, it earns points for structural economy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (5 optional params, output schema, and several siblings), the description is insufficient. It lacks usage guidelines, does not explain the concept of 'important updates' or 'factual engagement,' and does not complement the schema meaningfully, leaving agents uncertain about appropriate use and expected results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 80% (4 of 5 params have descriptions; limit lacks one but has min/max/default). The description adds no parameter information beyond what the schema provides, so it does not improve semantics. The baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool 'search important collected updates' with a verb and resource, but 'important' is vague and doesn't specify what constitutes 'updates' (though schema clarifies kinds). It doesn't differentiate from siblings like get_project_news or get_signal_timeline, which also deal with project updates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description only mentions ranking by 'factual engagement and labels,' which hints at a differentiator but does not explicitly state use cases, exclusions, or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'bounded' and 'recent' but does not explain bounding behavior, ordering, filters, or side effects. It does not state whether the operation is read-only or if permissions are required. The description does not contradict any annotations, but it provides minimal behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the primary purpose. It avoids redundancy with the schema and annotations. However, it sacrifices necessary detail for brevity, so it is not a perfect 5.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (3 parameters, output schema) and the existence of overlapping sibling tools, the description is too sparse. It does not explain what 'important Signals' means, how limits interact, or when to prefer this over get_signal_timeline. The output schema exists but the description still needs to set expectations for the combined result set, which it fails to do.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33% (only 'repository' has a description). The tool description adds no parameter-specific meaning, failing to link 'bounded important Signals' to signal_limit or 'recent Observation Events' to event_limit. The parameter names and schema defaults provide some semantics, but the description does not compensate for the low coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves project metadata plus important signals and observation events, using the specific verb 'Get.' It identifies distinct resources (metadata, Signals, Observation Events) which helps distinguish it from generic 'get' tools. However, it does not explicitly differentiate from siblings like get_signal_timeline, which may overlap on Signal retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparisons with sibling tools such as get_signal_timeline or search_project_updates. The usage context is only implied by the tool's name and brief description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must convey behavioral traits but only states that projects are listed with context and counts. It does not clarify what 'configured' means, whether the list is exhaustive or filtered, or what the output structure is, leaving key behaviors ambiguous.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no wasteful words. It is appropriately sized for a simple listing tool, though it omits important details, which are already captured in other dimensions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists, the description lacks essential context. It does not explain the notion of 'configured projects', the meaning of 'context' and 'collected evidence counts', or how the 'group' parameter affects the results, making it insufficient for full understanding.
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?
The input schema defines a 'group' parameter with no description (0% coverage). The description completely ignores this parameter, providing no clues about its meaning or valid values, thus failing to compensate for the schema's lack of documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: 'List configured projects'. It further specifies what is included ('context and collected evidence counts'), distinguishing it from sibling tools that focus on updates, context, opportunities, and timelines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or comparisons to sibling tools, leaving the agent without context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It only adds that data comes from the 'latest snapshot,' implying a non-live read operation, but it does not clarify output behavior, scoping, or whether only monitored projects are included.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. Every word contributes to stating the action and object.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one optional parameter) and has an output schema, so return-value details are not required. However, the description lacks context around when to use it, what 'Leads' means, and how the 'group' parameter scopes the comparison, leaving gaps for an agent deciding whether to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single optional 'group' parameter is already described as 'Exact configured project-group id.' The tool description adds no additional meaning about how group affects the comparison, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Compare') and identifies clear resources ('factual project context and Leads observed in the latest snapshot'), which conveys the tool's core function and distinguishes it from search/retrieval siblings. It loses a point because 'Leads' is left unexplained and there is no explicit contrast with sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to choose compare_projects over siblings like get_project_context, get_signal_timeline, or search_project_updates. There are no preferred scenarios, exclusions, or alternative tool references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries full burden. It only lists content types and does not disclose behavioral traits such as authentication requirements, filtering/grouping behavior, rate limits, or how the parameters affect results. The term 'public' hints at scope but is insufficient for a tool with optional group and project identifiers.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It concisely states the tool's purpose and distinct content types, making it easy to scan and understand.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Though an output schema exists, the description is minimal. For a tool with two identifiers (group and project) and overlapping siblings, more context would help disambiguate usage. The description is functional but not complete enough to fully guide an agent without additional investigation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is high (75%), with group, query, and project already described. The tool description adds minimal new meaning beyond the schema, mainly aligning query matching with the listed content types. Since the schema covers most parameters, a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Get' and enumerates the exact resources returned: releases, public roadmap items, and HN discussions. This clearly distinguishes it from siblings like search_project_updates or get_signal_timeline, which focus on updates or timeline events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. With sibling tools like search_project_updates and get_signal_timeline, the description does not mention when this is the appropriate choice or when to prefer another tool. No exclusions or alternative references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It indicates a read-only 'find' operation and mentions output contents, but does not disclose potential side effects, ordering, or error behavior. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that effectively captures the core purpose and key output features without unnecessary verbosity. Excellent structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides a high-level idea of the return content, but lacks details such as output format, pagination, or edge cases. Since no output schema is provided, more context could be beneficial, but it's not critically incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides descriptions for most parameters (tier, group, query, project), covering 80% of the params. The description adds no additional detail about parameter usage, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds open and unassigned contribution leads, and also mentions the output includes reasons, caveats, and evidence URLs, making the purpose distinct from sibling tools like search_project_updates or compare_projects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for discovering contribution opportunities but does not explicitly contrast with alternatives or specify when to prefer this tool over others. It relies on the tool's name and inferred context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the trail is 'append-only' (immutable/historical), which is useful, but does not explicitly state whether the tool is read-only, whether it has side effects, or any other behavioral details like ordering or pagination. It gives some context but not a rich behavioral profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence: 'Get the append-only discovery/change trail for a stable Signal ID.' Every word earns its place; no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter get-by-ID tool with an output schema, the description is largely sufficient. It covers the core purpose and the nature of the data (append-only trail). It could mention return ordering or include a note about pagination, but the word 'trail' implies a sequence, and the output schema presumably defines the structure. The tool's simplicity lowers the burden.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides only a bare string property 'signal_id' with 0% description coverage. The description adds the qualifier 'stable' to signal ID, hinting that the ID is persistent and not transient. However, it does not explain what a signal is, where to find the ID, or any format constraints, leaving the parameter semantically under-specified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Get' and names a clear resource: 'the append-only discovery/change trail for a stable Signal ID.' It differentiates from sibling tools like search_project_updates and get_project_context, which serve different purposes (searching updates vs. getting a timeline).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: this is for retrieving the change trail for a specific Signal ID. It doesn't explicitly state when not to use it or point to alternatives, but the 'append-only trail' phrasing strongly implies it's for historical/change tracking rather than, say, searching or listing projects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![contribution-compass MCP server](https://glama.ai/mcp/servers/amk9978/contribution-compass/badges/card.svg)](https://glama.ai/mcp/servers/amk9978/contribution-compass)

Score Badge

Copy to your README.md:

[![contribution-compass MCP server](https://glama.ai/mcp/servers/amk9978/contribution-compass/badges/score.svg)](https://glama.ai/mcp/servers/amk9978/contribution-compass)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/amk9978/contribution-compass'

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