Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GLAMA_API_KEYYesYour Glama API key
GLAMA_DEFAULT_MODELNoOptional default model to use, e.g. openai/gpt-4o

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
glama_list_modelsA

List the models available through the Glama gateway (OpenAI-format model ids).

glama_chat_completionC

Run a chat completion against the Glama gateway. messages is an array of {role, content} objects.

glama_stream_completionB

Streamed chat completion; deltas are reassembled into one text answer with usage metadata.

glama_request_statusC

Look up the status of a completion request by id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation4/5

list_models and request_status are clearly distinct, but chat_completion and stream_completion overlap in purpose as they both perform chat completions. The descriptions clarify streaming vs. non-streaming, so an agent can differentiate them, though some ambiguity remains.

Naming Consistency5/5

All tool names share the glama_ prefix and follow a consistent snake_case verb_noun pattern. The naming is predictable and uniform across the set.

Tool Count5/5

Four tools is well-scoped for a gateway-focused server covering model discovery, completion, streaming, and status lookup. Each tool has a clear, non-redundant role.

Completeness4/5

The core workflow of listing models and running both standard and streaming completions is covered, plus status lookup for async requests. Minor additions like request cancellation or model details would improve completeness, but no critical gap exists.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive