Schema | ndjson-local-log-triage-mcp

ndjson-local-log-triage-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
query_log_patternA	Filter NDJSON log file by field/value pattern, return top N matching entries.
detect_error_anomaliesB	Z-score frequency analysis to find sudden error spikes by time window.
summarize_log_timelineA	Chronological severity aggregation — errors, warnings, and info counts per time window.
correlate_requestA	Reconstruct a distributed trace by collecting all log events matching a trace/request ID across multiple NDJSON files, sorted chronologically.
discover_log_schemaB	Analyze a log file to infer format and type schemas, including key type polymorphism and regex patterns for timestamps.
group_semantic_patternsA	Cluster similar log messages using Drain algorithm to isolate core events and parameter distributions.
start_live_triageA	Start background log tailing with real-time Z-score anomaly alerting and heap memory safety limits.
query_external_logsA	Query external log providers (Datadog, Splunk, Elasticsearch) translating search patterns and mapping to OpenTelemetry format.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vola-trebla/ndjson-local-log-triage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server