Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_API_KEYNoYour Google AI API key
OPENAI_API_KEYNoYour OpenAI API key
OLLAMA_BASE_URLNoOllama instance URLhttp://localhost:11434
DEEPSEEK_API_KEYNoYour DeepSeek API key
ANTHROPIC_API_KEYNoYour Anthropic API key
OPENROUTER_API_KEYNoYour OpenRouter API key
OPENAI_COMPATIBLE_API_KEYNoAPI key for OpenAI-compatible services
OPENAI_COMPATIBLE_API_MODELSNoComma-separated list of available models for OpenAI-compatible services
OPENAI_COMPATIBLE_API_BASE_URLNoBase URL for OpenAI-compatible services

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
getSecondOpinionC

Get responses from various LLM providers

listProvidersA

List all configured LLM providers and their available models

listReasoningModelsB

List all available models that support reasoning capabilities

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: getSecondOpinion retrieves LLM responses, listProviders shows configured providers and models, and listReasoningModels specifically lists models with reasoning capabilities. There is no overlap in functionality, making tool selection unambiguous.

Naming Consistency4/5

The naming is mostly consistent with a verb_noun pattern (getSecondOpinion, listProviders, listReasoningModels), but getSecondOpinion uses camelCase while the others use a more descriptive phrase-based style. This minor deviation slightly affects consistency.

Tool Count3/5

With only 3 tools, the server feels thin for a domain involving LLM interactions, as it lacks operations like configuring providers, managing models, or performing other common tasks. However, the tools cover basic listing and querying functions, making it borderline appropriate.

Completeness2/5

The toolset is significantly incomplete for an LLM interaction server. It lacks core operations such as adding or removing providers, configuring models, or performing advanced queries beyond getSecondOpinion. This will likely cause agent failures when trying to manage or customize the LLM setup.

Maintenance

ActivityInactive
ResponsivenessUnresponsive