repo-scout
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_reposB | Search public GitHub repositories by keyword/topic. Returns stars, last-updated, license, etc. |
| get_repo_detailsA | Fetch details for one specific repo (owner/name), including README excerpt and top-level file list, so you can judge whether it fits your use case. |
| suggest_stackA | Given a plain-language description of what you're about to build, runs several targeted GitHub searches (including curated/awesome-list style queries) and returns a ranked shortlist of existing projects/libraries you could reuse instead of building from scratch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: retrieving details for a specific known repo, searching by keywords, and generating a shortlist from a natural-language description. No overlap in functionality or target resource.
All tool names follow a consistent verb_noun pattern in snake_case: get_repo_details, search_repos, suggest_stack. This is a predictable and uniform convention.
With only 3 tools, the server is tightly scoped to the 'repo scout' purpose: discovery (search), semantic suggestion (suggest), and evaluation (get details). Each tool earns its place, and the count is within the ideal 3-15 range.
The tool surface covers the full workflow for scouting repositories: finding candidates (search_repos, suggest_stack) and inspecting them (get_repo_details). No obvious gaps or dead ends for the stated purpose.