Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LLAMA_URLNollama-server base URL. Equivalent to the --url option.http://localhost:8080
LLAMA_MODELNoModel id to use when a tool call names none. Equivalent to the --model option. Required when llama-server runs in router mode (started without -m/-hf, offering several models); chat, complete and tokenize also take a per-call model argument.
LLAMA_API_KEYNoSent as a bearer token, for a llama-server started with --api-key.

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
chatC

Send a prompt to the local model through its chat template and return the reply.

    Leave `temperature` unset to use llama-server's own sampling settings.
    
completeB

Continue raw text with the local model, with no chat template applied.

    Leave `temperature` unset to use llama-server's own sampling settings.
    
tokenizeC

Return the model's token ids for text.

modelsA

List the models llama-server offers, with their status.

    A single-model llama-server always reports `loaded`. In router mode a model is `unloaded` until
    a request names it, and the first such request waits while it loads.
    
healthA

Report whether llama-server is up and has a model loaded.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 5 tools

Disambiguation4/5

chat and complete both send text to the model and return output, so their boundary rests entirely on the chat-template distinction, which the descriptions do clarify. tokenize, models, and health are each clearly distinct from that pair and from each other.

Naming Consistency3/5

All names are single lowercase words in a consistent casing style, which keeps them readable. However, the set mixes bare verbs (chat, complete, tokenize) with bare nouns (models, health) with no predictable verb_noun pattern.

Tool Count5/5

Five tools is well-scoped for a thin wrapper over a local llama-server: two generation modes, tokenizer access, model listing, and a health probe. Each tool earns its place with no obvious redundancy.

Completeness3/5

Core inference and diagnostics are covered, but common llama-server capabilities are absent: embeddings, explicit model selection/load-unload for router mode, and detokenization. Agents can still work around these gaps but will hit dead ends for embedding workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues