Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
XAI_API_KEYNoAPI key for xAI / Grok.
KIMI_API_KEYNoAPI key for Moonshot / Kimi. Providers without a key are unavailable, but the server can still run with the remaining providers.
GEMINI_API_KEYNoAPI key for Google Gemini.
DEEPSEEK_API_KEYNoAPI key for DeepSeek. DeepSeek is the default judge.

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
council_deliberateA

Run multi-model deliberation: several models answer a question in parallel, then a judge synthesizes the best answer. Use for high-stakes decisions, architecture questions, debugging strategy, or any question where hallucination risk matters.

council_list_modelsA

List the provider/model pairs available for deliberation.

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 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: one executes a deliberation, the other enumerates available models. There is no plausible way to confuse listing models with running a deliberation.

Naming Consistency5/5

Both names use the same 'council_' prefix followed by a clear verb_noun pattern (council_deliberate, council_list_models). The convention is predictable and readable.

Tool Count3/5

Two tools is thin for a server, though the domain (multi-model deliberation with a judge) is narrow enough that a discovery tool plus a single execution tool may genuinely be all that's needed. It sits at the borderline of minimal but defensible.

Completeness3/5

The surface covers the core operation and model discovery, but there is no way to inspect or retrieve prior deliberations, configure the judge/models per call, or check status of a long-running deliberation. These are notable gaps an agent could hit, though the primary workflow is usable.

Maintenance

ActivityMaintained
ResponsivenessOutdated data