Log Analyzer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| analyze_testsB | Analyze the most recent test run and provide detailed information about failures. |
| run_tests_no_verbosityA | Run all tests with minimal output (verbosity level 0). |
| run_tests_verboseB | Run all tests with verbose output (verbosity level 1). |
| run_tests_very_verboseB | Run all tests with very verbose output (verbosity level 2). |
| pingA | Check if the MCP server is alive. |
| create_coverage_reportB | |
| run_unit_testA | |
| search_log_all_recordsC | Search for all log records, optionally filtering by scope and content patterns, with context. |
| search_log_time_basedC | Search logs within a time window, optionally filtering, with context. |
| search_log_first_n_recordsC | Search for the first N (oldest) records, optionally filtering, with context. |
| search_log_last_n_recordsC | Search for the last N (newest) records, optionally filtering, with context. |
| get_server_env_detailsA | Returns sys.path and sys.executable from the running MCP server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
There is significant overlap between the test-running tools (run_tests_no_verbosity, run_tests_verbose, run_tests_very_verbose, run_unit_test) which could cause confusion about which to select for different verbosity needs. However, the search_log_* tools are well-differentiated by their temporal focus, and analyze_tests vs. create_coverage_report serve distinct purposes.
Most tools follow a consistent verb_noun pattern (analyze_tests, create_coverage_report, search_log_all_records, etc.). The main deviation is get_server_env_details which uses a get_ prefix instead of a more descriptive verb, and ping which is a single word outlier, but overall the naming is quite predictable.
12 tools is reasonable for a log analyzer server that also handles testing. While the count is appropriate, the distribution feels slightly imbalanced with many test-running tools and fewer log analysis tools, but it's still within a well-scoped range.
For log analysis, the search tools provide good temporal coverage but lack operations like log ingestion, filtering by severity, or aggregation. For testing, there are multiple execution tools but no tools for test setup, teardown, or result comparison. The surface covers core workflows but has notable gaps in both domains.