Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoServer port3157
LOG_LEVELNoLogging levelinfo
XAI_API_KEYNoX.AI API key
CODEX_API_KEYNoCodex API key (optional if ChatGPT login available)
GEMINI_API_KEYNoGoogle Gemini API key (takes priority over GOOGLE_API_KEY)
GOOGLE_API_KEYNoAlternative Google API key
OPENAI_API_KEYNoOpenAI API key
MISTRAL_API_KEYNoMistral API key
DEEPSEEK_API_KEYNoDeepSeek API key
MCP_TOOL_TIMEOUTNoTool timeout in ms (system-wide)
OPENROUTER_TITLENoOpenRouter title
ANTHROPIC_API_KEYNoAnthropic API key
CODEX_SANDBOX_MODENoCodex sandbox moderead-only
OPENROUTER_API_KEYNoOpenRouter API key
OPENROUTER_REFERERNoOpenRouter referer
SUMMARIZATION_MODELNoModel for summarizationgpt-5-nano
CODEX_SKIP_GIT_CHECKNoSkip git checktrue
CODEX_APPROVAL_POLICYNoCodex approval policynever
MAX_MCP_OUTPUT_TOKENSNoMax output tokens (system-wide)
OPENROUTER_DYNAMIC_MODELSNoEnable dynamic modelstrue
ENABLE_RESPONSE_SUMMARIZATIONNoEnable AI-generated summariesfalse

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
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
chatA

UNIFIED CHAT — talk to one or more AI models. mode "chat" (default): 1..N models answer independently in parallel. mode "consensus": ≥2 models answer, then refine after seeing each other. mode "roundtable": models answer sequentially, each building on the running transcript. Supports files, images, and continuation_id for multi-turn threads (you may switch modes on resume). Use model "auto" for automatic selection. IMPORTANT: use the "files" parameter to share code/file content instead of pasting into the prompt.

check_statusA

Check the status and progress of async jobs. Query specific jobs by continuation_id or list the 10 most recent jobs. Returns job status with start time and progress information.

cancel_jobA

Cancel a running async job by its continuation_id.

Terminates queued or running jobs with graceful cleanup. Preserves partial results when available.

decideA

DECIDE — ask a System One decision model (TypeSafe Jev) typed questions about a state and get calibrated answers, not text. Question types: "noul" (yes/no → probability 0..1), "choice" (pick one of 2–255 named options → choice, per-option probabilities, confidence), "score" (ordered rubric of 2–10 levels → weighted position, per-level probabilities, confidence). Batch independent questions over the same state into one call: they are judged in parallel and in isolation, so none sees another's answer; each extra question adds its own input tokens. Best for fast semantic judgments (classify, route, select, verify, rank). Ask one narrow, coherent judgment per question, with its full meaning in the question; split independently useful dimensions, but a bounded action choice or contextual interpretation is a valid single question. Do counting, arithmetic, and date comparison in code. confidence measures how concentrated the distribution is, not permission to act: take the top option to pick a best, and treat a noul near 0.5 as "yes and no equally likely". Text only, no explanations are returned. Limits: ~64k tokens per request, ~32k for state plus the longest question.

Prompts

Interactive templates invoked by user choice

NameDescription
helpComprehensive guide for Converse MCP Server - tools, models, parameters, and configuration

Resources

Contextual data attached and managed by the client

NameDescription
Help DocumentationComprehensive guide for the Converse MCP Server including all tools, parameters, providers, and models

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: chat handles model conversations, decide handles typed decision questions, and cancel_job/check_status manage async job lifecycle from opposite angles. Boundaries are reinforced by explicit modes and output types, so misselection is unlikely.

Naming Consistency4/5

All names use lowercase snake_case and readable verbs, but the pattern is not fully uniform: cancel_job and check_status follow verb_noun, while chat and decide are bare verbs. This is a minor deviation rather than a confusing mix.

Tool Count5/5

Four tools is well-scoped for a unified chat/decision server: chat, one async job control pair, and decide. Each tool has a clear role, and the surface does not feel thin or bloated.

Completeness4/5

Core capabilities are covered: multi-mode model chat, decision queries, and async job cancellation/status. A minor possible gap is explicit retrieval of completed async job results, though this may be handled through chat continuation_id.

Maintenance

ActivityActive
ResponsivenessNo issues