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

Find log patterns first seen within a recent window to isolate new issues without baseline noise. Use for 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.

Input Schema

TableJSON 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

TableJSON 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 readOnly/idempotent/openWorld, so safety is covered; the description still adds real behavioral value by defining what 'new' means (first_seen younger than first_seen_within), stating the default sort order (recency descending), and noting new patterns have no baseline. The fetchFirstSeenBatch/bytes_per_pattern plumbing is internal detail the caller does not need, which keeps this from a 5.

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?

Front-loaded correctly: purpose, then sibling differentiation, then semantics. However, the long implementation sentence ('queries bytes_per_pattern ... via fetchFirstSeenBatch') and the trailing list of returned fields are not needed for correct invocation and pad an otherwise tight description.

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?

Given 8 parameters, full schema coverage, an output schema, and complete annotations, the description covers everything an agent needs to choose and call the tool correctly. Return fields are listed redundantly (the output schema already has them) but nothing is missing.

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 all 8 parameters are already documented and the baseline is 3. The description's first_seen_within guidance (triage vs deploy review vs hygiene) duplicates the schema's own description text rather than adding new semantics.

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?

States the specific resource (patterns) and the exact selection criterion (first_seen inside a recency window) and pins down the question it answers: 'what showed up recently'. It explicitly names the two nearest siblings and contrasts them (cost ranking vs delta-vs-baseline), so an agent can route without opening schemas.

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 guidance keyed to concrete scenarios: '1h' for incident triage, '1d' for daily-deploy review, '7d+' for weekly observability hygiene. It also states when-not-to-use by naming log10x_top_patterns and log10x_whats_changing as the alternatives.

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

Deploy Server