Skip to main content
Glama
mothlike

MCP Graylog Server

by mothlike

aggregate_logs

Aggregate log entries by specified field and compute metrics such as count, average, sum, or percentile over a defined time range and streams.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aggregationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'aggregate_logs' tool handler function in ToolHandlers class. It delegates to GraylogClient.aggregate() passing the typed AggregateLogsInput model.
    def aggregate_logs(self, aggregation: AggregateLogsInput) -> dict[str, Any]:
        return self.graylog.aggregate(aggregation)
  • The AggregateLogsInput Pydantic model - defines schema/validation for the aggregate_logs tool input, including query, timerange, streams, field, metric, metric_field, percentile, and limit fields with validation logic.
    class AggregateLogsInput(BaseModel):
        query: str = Field("*", min_length=1)
        timerange: TimeRange = Field(
            default_factory=lambda: RelativeTimeRange.model_validate({})
        )
        streams: list[str] = Field(default_factory=list)
        field: str = Field(..., min_length=1)
        metric: Literal[
            "average",
            "avg",
            "count",
            "latest",
            "max",
            "min",
            "percentile",
            "stdDev",
            "sum",
            "sumOfSquares",
            "variance",
        ] = "count"
        metric_field: str | None = Field(
            None,
            description="Target field for non-count Graylog aggregation metrics.",
        )
        percentile: float | None = Field(
            None,
            ge=0,
            le=100,
            description="Percentile value used when metric is percentile.",
        )
        limit: int = Field(10, ge=1, le=100)
    
        @field_validator("query")
        @classmethod
        def strip_query(cls, value: str) -> str:
            stripped = value.strip()
            if not stripped:
                raise ValueError("query must not be empty")
            return stripped
    
        @model_validator(mode="after")
        def validate_metric_configuration(self) -> "AggregateLogsInput":
            if self.metric != "count" and not self.metric_field:
                raise ValueError("metric_field is required for non-count metrics")
            if self.metric == "percentile" and self.percentile is None:
                raise ValueError("percentile is required for percentile metrics")
            if self.metric != "percentile" and self.percentile is not None:
                raise ValueError("percentile is only valid for percentile metrics")
            return self
    
        def to_graylog_payload(self) -> dict[str, object]:
            metric: dict[str, object] = {"function": self.metric}
            if self.metric_field:
                metric["field"] = self.metric_field
            if self.percentile is not None:
                metric["configuration"] = {"percentile": self.percentile}
    
            payload: dict[str, object] = {
                "query": self.query,
                "timerange": self.timerange.to_graylog(),
                "group_by": [{"field": self.field, "limit": self.limit}],
                "metrics": [metric],
            }
            if self.streams:
                payload["streams"] = list(self.streams)
            return payload
  • Registration of aggregate_logs as an MCP tool on the FastMCP server. Line 130: mcp.tool()(handlers.aggregate_logs)
    mcp.tool()(handlers.search_logs)
    mcp.tool()(handlers.search_stream_logs)
    mcp.tool()(handlers.aggregate_logs)
  • The GraylogClient.aggregate() method that makes the actual HTTP POST request to Graylog's /api/search/aggregate endpoint using the payload built by AggregateLogsInput.to_graylog_payload().
    def aggregate(self, aggregation: AggregateLogsInput) -> dict[str, Any]:
        return self._request(
            "POST",
            "/api/search/aggregate",
            json=aggregation.to_graylog_payload(),
        )
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mothlike/mcp-graylog'

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