Skip to main content
Glama
truaxki
by truaxki

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.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
log-queryC
            Conversation Variation analysis
            Continuously monitor our conversation and automatically log unusual or noteworthy interactions based on the following criteria:

            1. Probability Classifications:
            HIGH (Not Logged):
            - Common questions and responses
            - Standard technical inquiries
            - Regular clarifications
            - Normal conversation flow

            MEDIUM (Logged):
            - Unexpected but plausible technical issues
            - Unusual patterns in user behavior
            - Noteworthy insights or connections
            - Edge cases in normal usage
            - Uncommon but valid use cases

            LOW (Logged with Priority):
            - Highly unusual technical phenomena
            - Potentially problematic patterns
            - Critical edge cases
            - Unexpected system behaviors
            - Novel or unique use cases
        
read-logsB

Retrieve logged conversation variations from the database.

read_queryA

Execute a SELECT query on the SQLite database

            Schema Reference:
            Table: chat_monitoring
            Fields:
            - log_id (INTEGER PRIMARY KEY)
            - timestamp (DATETIME)
            - session_id (TEXT)
            - user_id (TEXT)
            - interaction_type (TEXT)
            - probability_class (TEXT: HIGH, MEDIUM, LOW)
            - message_content (TEXT)
            - response_content (TEXT)
            - context_summary (TEXT)
            - reasoning (TEXT)

            Example:
            SELECT timestamp, probability_class, context_summary 
            FROM chat_monitoring 
            WHERE probability_class = 'LOW'
            LIMIT 5;
            
write_queryC

Execute an INSERT, UPDATE, or DELETE query

create_tableC

Create a new table in the SQLite database

list_tablesA

List all tables in the database

describe_tableC

Show structure of a specific table

append_insightB

Add a business insight to the memo

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 8 tools

Disambiguation3/5

Most tools have distinct purposes (e.g., create_table vs. list_tables), but there is overlap between log-query and read-logs, as both involve logging/retrieving conversation variations, which could cause confusion. Additionally, read_query and write_query are clearly distinct from each other but share the database query domain with other tools like describe_table.

Naming Consistency2/5

Naming is inconsistent with mixed conventions: some use snake_case (append_insight, create_table), others use kebab-case (log-query, read-logs), and some are unclear (read_query vs. write_query, which are snake_case but differ in verb style). There is no uniform pattern across all tools, making it harder to predict naming.

Tool Count4/5

With 8 tools, the count is reasonable for a server focused on database operations and conversation logging. It covers core functions without being overly bloated, though the scope might feel slightly broad due to mixing database management with logging features.

Completeness3/5

For database operations, there is good coverage (create, list, describe, read, write), but lacks update/delete specific tools, relying on write_query for those. For conversation logging, it has logging and retrieval, but no direct management tools like delete_logs or update_logs, leaving minor gaps in the lifecycle.

Maintenance

ActivityInactive
ResponsivenessNo issues