Skip to main content
Glama
Pu11en

all-git

by Pu11en

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALLGIT_HOMENoSet ALLGIT_HOME to relocate the catalog.
GITHUB_TOKENNoSet GITHUB_TOKEN to raise the enrichment budget for GitHub metadata.

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
search_reposA

Search the GitHub Awesome catalog for repositories matching a need, for example 'cold email', 'self-hosted analytics', or 'logo SVG'. Returns curated repos with links, optional stars, and timestamped video evidence of why each is good.

get_repoA

Fetch one repository's catalog entry: owner/name (for example 'coffinxp/crtmon'), stars, language, and every video mention with a timestamped link and caption excerpt.

get_catalog_statusA

Read local catalog coverage numbers: videos, descriptions, captioned videos, repos, mentions, and enrichment counts. Never contacts the network.

update_catalogA

Sync the catalog with the GitHub Awesome channel: fetch new videos' descriptions and captions, resolve new repos, then optionally enrich repos with GitHub metadata (stars, language, dead links). Enrichment uses GITHUB_TOKEN when present; without it only a small unauthenticated budget is spent. Report the returned counts to the user.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct action: single repo lookup, catalog search, status inspection, and full catalog sync. There is no meaningful overlap, and the descriptions make selection straightforward.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_repo, search_repos, get_catalog_status, update_catalog. The singular/plural variation is natural and predictable.

Tool Count5/5

Four tools is small but well-suited to the narrow scope of a curated repository catalog. Each tool fills a clear role and none feels redundant.

Completeness4/5

The core catalog workflow is covered: find, fetch, inspect status, and update. A generic list-all-repositories or direct video-detail tool is missing, but agents can work around this through search and repo-level lookups.

Maintenance

ActivityMaintained
ResponsivenessNo issues