Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MINION_METANoSet to 1 to add a _minion key (votes, judge used) to results.
MINION_MODELYesModel name as the backend knows it. Required.
MINION_ROSTERNoInline JSON or a path to a JSON file to use several models. Without it, the single-model setup applies unchanged.
MINION_BACKENDNoBackend to use: lmstudio or ollama.lmstudio
MINION_TIMEOUTNoSeconds to wait for the model.120
MINION_BASE_URLNoOpenAI-compatible root URL, ending in /v1. Defaults to http://127.0.0.1:1234/v1 for LM Studio or http://127.0.0.1:11434/v1 for Ollama.
MINION_OLLAMA_NATIVENoSet to 1 to use Ollama's native /api/chat format instead of response_format.
MINION_MAX_FILE_BYTESNoSize cap for the *_file tools.1000000

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
classifyC

Classify text into exactly one of the given labels using a local model.

extractC

Extract fields from text into an object matching a JSON Schema (type: object).

summarizeC

Summarize text in at most max_words words.

classify_fileB

Like classify, reading UTF-8 text from a local file (size-capped).

extract_fileB

Like extract, reading UTF-8 text from a local file (size-capped).

summarize_fileB

Like summarize, reading UTF-8 text from a local file (size-capped).

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

Disambiguation5/5

classify, extract, and summarize target three clearly distinct operations (classification, schema-based field extraction, summarization), and each _file variant is explicitly documented as the same operation with a file input source. There is no real ambiguity about which tool performs which action.

Naming Consistency5/5

All names use a consistent snake_case verb pattern, with the _file suffix applied uniformly to denote the file-reading variant of each operation. The taxonomy is predictable and readable.

Tool Count5/5

Six tools for three core text operations plus their file counterparts is tight and well-scoped; every tool earns its place with no redundancy beyond the intended input-source pairing.

Completeness4/5

The surface covers the three primary operations for both raw text and local files, forming a coherent lifecycle. Minor gaps exist (e.g. no batch, URL, or stdin input variants), but agents can work around them by reading content themselves.

Maintenance

ActivityMaintained
ResponsivenessNo issues