Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITLAB_HOSTNoGitLab host URL, default is gitlab.com, for self-hosted instancesgitlab.com
GITHUB_TOKENNoGitHub personal access token, required when using GitHub
GITLAB_TOKENNoGitLab personal access token, required when using GitLab
CODE_REVIEW_RULES_DIRNoPath to custom review rules directory

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

Tools

Functions exposed to the LLM to take actions

NameDescription
get_review_rulesA

Get code review rules (builtin + custom project rules). Call this before starting a review to load all applicable rules. Custom rules are loaded from CODE_REVIEW_RULES_DIR env var, or auto-discovered from .code-review-rules/ in the working directory.

get_pr_infoA

Get PR/MR detailed information including title, description, author, and branches

get_pr_changesA

Get PR/MR code changes (diff) with optional file extension filtering

add_inline_commentA

Add inline comment to a specific code line in PR/MR

add_pr_commentB

Add a general comment to PR/MR

batch_add_commentsA

Batch add multiple inline comments and optionally a general comment

extract_related_prsA

Extract related PR/MR links from description text

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: inline comments, general comments, batch comments, extracting PR links, getting PR changes, PR info, and review rules. No ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., add_inline_comment, get_pr_changes), making them predictable and easy to understand.

Tool Count5/5

Seven tools is well-scoped for a code review server, covering commenting, information retrieval, and rule loading without unnecessary bloat.

Completeness4/5

The tool set covers core review operations (viewing info, changes, adding comments, rules), but lacks edit/delete comment functionality, which is a minor gap.

Maintenance

ActivityMaintained
ResponsivenessNo issues