Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GROK_MODELNoModel ID for Grok backend.
CODEX_MODELNoModel ID for Codex backend.
DEEPSEEK_MODELNoModel ID for DeepSeek/local backend.
CLIPROXY_API_KEYYesA long random client key for CLIProxyAPI.
CLIPROXY_BASE_URLNoBase URL of CLIProxyAPI.http://127.0.0.1:8317/v1

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
delegate_analysisA

Ask Codex, Grok, or local DeepSeek for independent analysis.

Use for debugging hypotheses, architecture evaluation, repository reasoning, or a second opinion. The external model cannot inspect files beyond the supplied context and cannot modify the workspace.

delegate_reviewA

Request a read-only code review from one external model.

Use for correctness, regression, security, concurrency, data-loss, or missing-test review. Claude must verify each material finding.

delegate_patchA

Ask an external model to propose a minimal unified diff.

This tool does not apply changes. Claude must inspect, validate, apply, format, test, and review any proposed patch.

compare_modelsA

Ask two or three external models the same question in parallel.

Use when independent opinions materially improve confidence. Claude must compare the outputs, verify claims against the repository, and synthesize the final conclusion.

list_companion_modelsA

List model IDs exposed by CLIProxyAPI and show whether the configured Codex, Grok, and DeepSeek models are currently available.

health_checkA

Verify connectivity to CLIProxyAPI and availability of configured companion models. This performs no model inference.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct primary purpose: analysis, review, patch, comparison, listing, and health checking. The slight overlap between delegate_analysis and delegate_review is mitigated by clear use-case descriptions, and list_companion_models/health_check serve different aspects of availability.

Naming Consistency4/5

Most names follow a verb_noun pattern (delegate_*, compare_models, list_companion_models), but health_check deviates from the verb-first convention and could be check_health. Overall the pattern is consistent enough to be predictable.

Tool Count5/5

Six tools is a well-scoped set for a multi-model companion server. Each tool covers a distinct capability without redundancy or bloat.

Completeness4/5

The server covers the primary workflows: delegating analysis, review, patch generation, multi-model comparison, and status checks. Minor gaps exist, such as no explicit tool for configuring models or retrieving detailed model metadata, but the core functionality is complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues