Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REPO_FORENSICS_ROOTNoExplicit workspace root. By default, paths must stay under the parent workspace of the package process.

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
repository_summaryA

Read branch, working-tree, remote names, and latest commit metadata from a local Git repository.

recent_changesB

List recent local Git commits with bounded output.

file_hotspotsA

Find files that appear most often in recent repository history. This is a heuristic for review focus, not a defect detector.

top_level_hygieneA

Check top-level large files, .gitignore presence, and working-tree dirtiness without reading file contents.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct aspect of repository forensics: overall state, recent history, file hotspots, and top-level hygiene. There is no overlap in their functions, making them easy to distinguish.

Naming Consistency4/5

All names use snake_case and are descriptive, but they mix noun phrases (repository_summary, file_hotspots) with adjective-noun forms (recent_changes, top_level_hygiene). The pattern is not strictly verb_noun, but it is readable and consistent in style.

Tool Count5/5

With only 4 tools, the server is well-scoped for a focused forensics purpose. Each tool provides a distinct slice of information without unnecessary bloat.

Completeness4/5

The set covers the basic forensics workflow: repo overview, change history, hotspot identification, and hygiene checks. Minor gaps exist, such as lacking diff or blame tools for deeper investigation, but the current surface is functional for its stated purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues