gts-repo-guardian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token for accessing repositories. |
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 |
|---|---|
| review_repositoryA | Analiza un repositorio GitHub y genera informe de calidad con puntuación 0-100 |
| generate_readmeB | Genera un README profesional automáticamente basado en el código del repo |
| clean_repositoryC | Limpia y estructura un repositorio automáticamente |
| review_all_repositoriesA | Revisa todos los repos públicos de un perfil GitHub |
| apply_improvementsB | Aplica las mejoras automáticamente basándose en el informe de review |
| watch_repositoriesC | Monitoriza repos y alerta sobre problemas |
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 6 tools
Most tools are clearly distinct: review, generate README, clean, bulk review, apply improvements, and watch. The main overlap is between clean_repository and apply_improvements, both of which modify a repo, though their stated intents are different enough to be workable.
All tool names follow a consistent snake_case verb_noun pattern, such as review_repository, generate_readme, and watch_repositories. The naming is predictable and makes the action of each tool immediately clear.
Six tools is well within the ideal range for a focused repo management server. Each tool covers a distinct part of the repo guarding workflow without unnecessary bloat.
The surface covers core lifecycle needs: review, improve, clean, document, bulk review, and monitor repos. Missing pieces like rollback/revert or report retrieval are minor and can be worked around.