Log10x MCP Server

Official

by log-10x

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

What's new: patterns by first_seen recency

log10x_whats_new

Read-onlyIdempotent

Detect log patterns whose first_seen timestamp falls inside a recency window, supporting incident triage, deploy review, and observability hygiene.

Instructions

Patterns whose first_seen timestamp falls inside a recency window: the "what showed up recently" question. Distinct from log10x_top_patterns (current cost ranking) and log10x_whats_changing (delta vs baseline). New patterns have no baseline, so delta math is meaningless; this tool exists so they get a clean home and don't pollute the changing-vs-baseline surface. Implementation: queries bytes_per_pattern in the current timeRange window to find candidate hashes, then for each hash queries the 30-day history to find the earliest non-zero datapoint via fetchFirstSeenBatch. A pattern is "new" when its first_seen timestamp is younger than first_seen_within (default 1d). Default sort: by first_seen recency descending (most recent first). Use first_seen_within: "1h" for incident triage, "1d" for daily-deploy review, "7d"+ for weekly observability hygiene. Returns patterns with first_seen, age, cost_now_usd, bytes_now, events_now, and the service + severity attribution. An engine upgrade that changes the naming rules renames the patterns it affects once, so the first windows after it list those patterns here as new, first seen from the upgrade on.

Input Schema

Name	Required	Description	Default
`view`	No	Output format.	summary
`limit`	No	Max patterns to return. Default 10.
`service`	No	Service name to scope the result. Omit for all services.
`severity`	No	Severity level to scope (e.g. `ERROR`, `CRITICAL`).
`timeRange`	No	Time range used to score current cost. Default 1h.	1h
`environment`	No	Environment nickname (for multi-env setups).
`analyzerCost`	No	SIEM ingestion cost in $/GB. Auto-detected from profile if omitted.
`first_seen_within`	No	Patterns whose first-seen timestamp is younger than this are "new." Default `1d`. Use `1h` for incident triage, `1d` for daily-deploy review, `7d`+ for weekly observability hygiene.	1d

Output Schema

Name	Required	Default
`data`	No
`tool`	Yes
`view`	No	summary
`images`	No
`actions`	No
`summary`	Yes
`warnings`	No
`truncated`	No
`next_cursor`	No
`render_hint`	No
`generated_at`	Yes
`schema_epoch`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.30.7Sep 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so safety is covered. Beyond that, the description adds real behavioral context: the query strategy (candidate hashes from bytes_per_pattern, then 30-day history via fetchFirstSeenBatch) and, most valuably, the engine-upgrade caveat that renamed patterns will appear as 'new' once. That caveat is a genuine gotcha not derivable from structured fields.

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

Conciseness4/5

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

Purpose, sibling differentiation, and the triage/review usage mapping are front-loaded before the implementation detail. It is a single dense paragraph and the fetchFirstSeenBatch internal is arguably expendable, but nearly every sentence carries actionable information.

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

Completeness5/5

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

All eight parameters are covered by the schema, an output schema exists, and the description still supplies selection guidance, newness definition, default sort, and edge-case behavior. An agent has everything needed to call and interpret this tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented, including the `first_seen_within` triage/review/hygiene guidance the description repeats. The description clarifies the definition of 'new' and the default sort, but adds little parameter meaning beyond the schema, so baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific resource and scope ("patterns whose first_seen timestamp falls inside a recency window") and explicitly names the two siblings it is not (`log10x_top_patterns`, `log10x_whats_changing`), with the reason for the split. An agent can distinguish it from alternatives without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use mapping: `first_seen_within: "1h"` for incident triage, `"1d"` for daily-deploy review, `"7d"+` for weekly hygiene. It also explains when NOT to use it (new patterns have no baseline, so delta math is meaningless), routing those cases to the delta sibling.

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

Deploy Server