Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read-only access to synthetic incident data: logs, tickets and runbooks. Every record has a stable ID (INC-…, LOG-…, TKT-…, RB-…); cite those IDs as evidence.

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
search_logsA

Search one incident's logs. Read-only and paginated, in timestamp order.

    No match is not an error: it returns total_matches 0. Each record carries its LOG- ID.
    
get_ticketA

Get one ticket, with its body and comments. Read-only.

    An incident's ticket IDs are listed in its incident://<incident_id> resource.
    
get_runbookA

Get one runbook: the symptoms it covers and its steps. Read-only.

    An incident's runbook IDs are listed in its incident://<incident_id> resource.
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
INC-0001
INC-0002

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct artifact: logs, a ticket, or a runbook. The read-only nature and ID sourcing from the incident resource further separate their roles, leaving no realistic overlap.

Naming Consistency5/5

All names follow a consistent snake_case verb_noun pattern: search_logs, get_ticket, get_runbook. The verb and plural/singular choices match the artifact semantics without introducing ambiguity.

Tool Count5/5

Three tools is lean but well within the appropriate range for a focused incident-investigation server. Each tool has a distinct, necessary role and none appears redundant.

Completeness3/5

The set covers read-only retrieval of logs, tickets, and runbooks, but lacks incident-level tools and any write operations such as updating tickets, commenting, or changing incident status. The incident resource helps anchor IDs, but the tool surface remains notably incomplete for full incident lifecycle work.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues