MCP server that finds open source issues where beginners actually succeed
GFI Scout demonstrates solid tool design with clear naming (verb_noun pattern), comprehensive parameter schemas, and well-structured output types. All four tools have descriptions and input schemas with type definitions. However, parameter descriptions lack actionable constraints (enums, ranges, formats), and error handling guidance is minimal. Output schemas are inferred from type hints rather than explicitly documented in descriptions. The server follows good composition patterns (single responsibility per tool) but misses opportunities for LLM-friendly constraint documentation.
Check whether a specific GitHub issue is actually available to work on.
Analyse a repository's contributor-friendliness.
Find beginner-friendly open source issues ranked by likelihood of success. Searches GitHub for "good first issue" labelled issues, scores each by repo health + freshness + clarity + merge friendliness + setup ease, and returns the top results.
Pull and summarise a repo's contribution guide + setup instructions.
Parameter descriptions lack actionable constraints. 'sort_by' accepts string but no enum values documented in description; 'max_results' has no range constraint stated (1-25 exists in code but not in param description); 'labels' default is null but description says 'Default ["good first issue"]', mismatch.
Output schemas not documented in tool descriptions. LLMs cannot see what fields RepoHealth, IssueStatus, ContributionGuide, or IssueResult contain without reading type definitions. Descriptions should state 'Returns: {field1: type, field2: type, ...}' or reference a schema.
No error handling guidance. Tool descriptions do not explain what happens on failure (e.g., invalid GitHub token, rate limit, repo not found, malformed URL). LLMs have no recovery path.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | <=2025-11-25 | v2 |
Parameter 'repo' in check_repo_health and get_contribution_guide accepts only 'owner/repo' format but description does not state this constraint or provide format guidance. LLMs may pass invalid formats.
Parameter 'issue_url' in check_issue_status lacks format constraint. Description says 'Full GitHub issue URL' but does not specify expected format (https://github.com/owner/repo/issues/123) or what happens if URL is malformed.