Skip to main content
Glama
ArminDashti
by ArminDashti

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AI_AGENT_LOGS_API_URLNoThe URL of the ai-agent-logs API.http://127.0.0.1:8120
AI_AGENT_LOGS_PASSWORDNoPassword for authenticating with the ai-agent-logs API.dopadopa123
AI_AGENT_LOGS_USERNAMENoUsername for authenticating with the ai-agent-logs API.armin

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
health_checkA

Check ai-agent-logs-api health (GET /health).

loginA

Login to ai-agent-logs-api and cache the JWT. Optional username/password override env defaults.

list_promptsA

List stored prompts newest first (GET /api/v1/prompts). Auto-logs in if needed.

create_promptA

Create a prompt log row (POST /api/v1/prompts). Auto-logs in if needed.

list_sessionsA

List agent conversation sessions newest first (GET /api/v1/sessions). Auto-logs in if needed.

get_sessionA

Get one session and its prompt turns (GET /api/v1/sessions/:id). Auto-logs in if needed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource and action: health_check for API status, login for authentication, list/create for prompts, and list/get for sessions. No overlap or ambiguity among them.

Naming Consistency5/5

All tool names follow a predictable lowercase_with_underscores pattern, mostly verb_noun (list_prompts, create_prompt, get_session). The singular 'login' and compound 'health_check' fit naturally without breaking consistency.

Tool Count5/5

With only 6 tools, the set is tightly scoped for the purpose of a logs API. Each tool serves an essential function, and the count is well within the ideal range.

Completeness4/5

The surface covers core prompt and session operations (list/create for prompts, list/get for sessions) plus health and login. Missing a get_prompt or delete operations, but for a logging server these are often unnecessary, making the gaps minor.

Maintenance

ActivityMaintained
ResponsivenessNo issues