Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENROUTER_API_KEYNoYour own OpenRouter API key; read from env only, never stored. Optional, required only for the optional probe command.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
list_free_modelsC

List currently free models from the live OpenRouter catalog. Optionally require tool calling and a minimum context length.

free_model_changesA

Diff the live free catalog against the last local scan: which free models appeared or disappeared. Free lineups rotate; check before hard-coding a model id.

free_providersA

Curated, human-verified free tiers for providers without a public catalog API (Groq, Gemini, NVIDIA NIM, Mistral, Cloudflare, Cohere), with limits, card rules and catches, each with source and verified date.

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

Disambiguation4/5

Each tool targets a distinct concern: live catalog listing, a delta against the previous scan, and curated static provider info. The only mild overlap is between list_free_models and free_model_changes, since the diff presumably builds on the same catalog, but descriptions make the boundary clear.

Naming Consistency3/5

list_free_models follows a verb_noun pattern while free_model_changes and free_providers are bare noun phrases, so the convention is mixed. Names remain short and readable, and the shared 'free' prefix gives topical coherence.

Tool Count4/5

Three tools is lean but each covers a genuinely different access mode (live query, historical diff, curated reference). The scope is narrow enough that this isn't bloated, though it sits at the thin end of the range.

Completeness3/5

The surface has a notable gap: free_model_changes diffs against 'the last local scan' but there is no tool to perform or update a scan/baseline, so the diff can be a dead end. There is also no lookup for a single model's details or pricing limits beyond raw listing.

Maintenance

ActivityMaintained
ResponsivenessNo issues