Skip to main content
Glama
Rajveerx11

gfi-scout

by Rajveerx11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENNoGitHub personal access token with public_repo scope (read-only) for higher rate limits. Optional.

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_issuesA

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.

Args:
    language: Programming language (e.g. "python", "typescript").
    min_stars: Minimum repo stars. Default 50.
    max_stars: Maximum repo stars. Default 50000.
    labels: Issue labels to require. Default ["good first issue"].
    max_results: How many results (1-25).
    sort_by: "beginner_score" | "freshness" | "repo_health".
    topic: Optional GitHub topic filter ("web", "cli", "data-science", ...).
    unassigned_only: When True (default), excludes issues that already
        have an assignee. Set False to widen the search when narrow
        language/label/stars combos return zero hits.
check_repo_healthB

Analyse a repository's contributor-friendliness.

Args:
    repo: Full repo name, e.g. "fastapi/fastapi".
check_issue_statusA

Check whether a specific GitHub issue is actually available to work on.

Args:
    issue_url: Full GitHub issue URL.
get_contribution_guideA

Pull and summarise a repo's contribution guide + setup instructions.

Args:
    repo: Full repo name, e.g. "fastapi/fastapi".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct task: repo health analysis, issue availability check, contribution guide retrieval, and issue search. There is no ambiguity or overlap between their purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (check_, check_, get_, find_), making the API predictable and easy to navigate.

Tool Count5/5

With 4 tools, the server is well-scoped for its specialized purpose of scouting good first issues. Each tool serves a clear role and no tool feels superfluous or missing for the core workflow.

Completeness4/5

The tool set covers the key workflow: finding candidate issues, checking repo health, verifying issue availability, and getting setup guidance. A minor gap is lack of direct issue content retrieval, but the existing tools enable a complete scouting flow.

Maintenance

ActivityMaintained
ResponsivenessWithin a week

Resources