Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPS_RUNBOOKNoJSON file the runbook tools read and write../data/runbook.json
OPS_LOG_ROOTNoDirectory tail_log is allowed to read from. Set it to /var/log on a real host../sample-logs

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
tail_logA

Read the last N lines of a log file under the configured log root, optionally filtered to lines containing a substring (case-insensitive).

check_endpointA

Request a URL and report whether it returned the expected status code, plus how long it took. Use it to confirm a service is actually answering, not just running.

runbook_searchA

Search the local runbook of known symptoms and their fixes. Use this before diagnosing an issue from scratch, since a past fix is usually faster than a fresh investigation.

runbook_addA

Record a new symptom and its fix in the local runbook so the next person does not have to rediscover it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct operation: log tailing, endpoint checking, and runbook search/add. There is no overlap in purpose or resource type.

Naming Consistency4/5

Names are clear and readable, but they follow two patterns: verb_noun (tail_log, check_endpoint) and noun_verb (runbook_search, runbook_add). This minor inconsistency is not confusing but prevents a perfect score.

Tool Count5/5

With 4 tools, the set is well-scoped for an operations toolbox. Each tool serves a clear purpose without redundancy or bloat.

Completeness4/5

The set covers the primary operations for its domain: log inspection, endpoint validation, and runbook management (search/add). Minor gaps like runbook deletion exist, but the core workflow is complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues