Skip to main content
Glama
mfreeman451

JSON Logs MCP Server

by mfreeman451

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
query_logsC

Search and filter log entries across log files

aggregate_logsC

Aggregate log data by specified criteria

get_log_statsC

Get overall statistics for log files

list_log_filesB

List available log files with metadata

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

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: list_log_files enumerates files, query_logs searches entries, aggregate_logs groups data, and get_log_stats provides statistics. The descriptions reinforce these boundaries, making tool selection unambiguous.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case (e.g., list_log_files, query_logs). The naming is predictable and readable, using clear verbs like 'list', 'query', 'aggregate', and 'get' that align with their actions.

Tool Count5/5

With 4 tools, this server is well-scoped for handling JSON logs. Each tool serves a distinct function in the log management workflow, from listing files to querying and analyzing data, without being overly sparse or bloated.

Completeness4/5

The toolset covers core log operations: listing files, querying entries, aggregating data, and getting statistics. A minor gap exists in lifecycle management (e.g., no tools for creating, updating, or deleting logs), but agents can likely work with the provided read/analyze functions.

Maintenance

ActivityInactive
ResponsivenessNo issues