Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GROQ_API_KEYYesFree key at https://console.groq.com/keys
CODEPECKER_TEXT_MODELNoOverride model/provider, e.g. openai/gpt-4o or ollama/llama3.1

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
review_and_remediateA

Review code across security, standards, readiness, and sustainability; automatically fix the issues; verify the fix by running its tests; and return the findings, a per-dimension scorecard over all rules (passes included, for coverage attestation), the remediated code, a diff, citations, and a metrics-style summary.

Args: code: the source code to review. language: the source language (default: python). tests: optional — the code's test suite if it lives in a separate file. Provide it so the review runs the tests (they should import the code as solution, e.g. from solution import ...) and doesn't false-positive on "no tests detected". tests_dir: optional — path to the code's test directory. Confirms tests are present (RDY-03) WITHOUT running them; this is how coverage is attested in detect-only mode (CODEPECKER_REMEDIATE=false), which skips test execution. support_files: optional {filename: source} of sibling modules the code (or its tests) imports — e.g. {"crypto.py": "...", "db.py": "..."}. They're written into the sandbox next to the code so a local from crypto import ... resolves instead of crashing test collection. Local files only; nothing is installed from a package index.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of selecting the wrong tool. The tool's purpose is clearly defined, covering review and remediation in a single action.

Naming Consistency5/5

The single tool name 'review_and_remediate' follows a clear verb_noun pattern, and consistency is trivially maintained with only one tool.

Tool Count3/5

The server has just one tool, which is below the typical 3-15 range. However, the tool is comprehensive, encapsulating review, remediation, verification, and reporting, so the thin count is acceptable for a focused purpose.

Completeness4/5

The tool covers the full lifecycle from code review to remediation to test verification, and returns a detailed scorecard and diff. Minor gaps include the inability to separate review-only from remediation, but an environment variable supports detect-only mode, so core workflows are covered.

Maintenance

ActivitySlowing
ResponsivenessNo issues