Log10x MCP Server

Official

by log-10x

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

What's changing: patterns ranked by delta vs baseline

log10x_whats_changing

Read-onlyIdempotent

Ranks log patterns by change versus a baseline to reveal what grew or shrank, such as post-deploy regressions or week-over-week cost drivers.

Instructions

Patterns ranked by delta vs a baseline window: the "what grew (or shrank) the most since X" question. Distinct from log10x_top_patterns which ranks by current cost; this tool ranks by delta and applies gates (min_delta_usd, min_delta_contribution_pct) that drop noise-level changes. comparison_window: "auto" (default) averages three offsets (1×, 2×, 3× the timeRange) for noise smoothing; specific offsets like "7d" compare to a single anchor, e.g. {timeRange: "1d", comparison_window: "1d"} is today vs yesterday (deploy-delta), {timeRange: "7d", comparison_window: "7d"} is this week vs last week. Brand-new patterns (no baseline samples) are EXCLUDED: they go to log10x_whats_new for clean separation of stories. Use for "what grew most this week", "which patterns regressed after the deploy", "what's driving cost up since yesterday". Returns patterns with per-row delta_usd, baseline_usd, current_usd, delta_pct, and a flag for whether each row crossed the contribution gate.

Input Schema

Name	Required	Description	Default
`view`	No	Output format. `summary` returns the structured envelope; `markdown` returns a rendered table.	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	Current window to evaluate. Day-level only: delta math requires day-aligned baseline offsets. For sub-day spike investigation use `log10x_pattern_trend` or `log10x_investigate`.	7d
`environment`	No	Environment nickname (for multi-env setups).
`analyzerCost`	No	SIEM ingestion cost in $/GB. Auto-detected from profile if omitted.
`min_delta_usd`	No	Dollar floor for delta. Rows with delta < min_delta_usd are dropped. Default $500/wk scaled to the selected timeRange window. Set to 0 to disable.
`comparison_window`	No	Baseline window to compare against. `"auto"` (default) averages three offsets (1×, 2×, 3× the timeRange) for noise smoothing. A specific offset like `"7d"` compares to that single anchor: e.g. `{timeRange: "1d", comparison_window: "1d"}` = today vs yesterday (deploy-delta); `{timeRange: "7d", comparison_window: "7d"}` = this week vs last week.	auto
`min_delta_contribution_pct`	No	Contribution gate as a percentage. A row's delta must be at least this fraction of total positive delta to be surfaced. Default 5. Set to 0 to disable.

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.

Changed2 schema fields changedv1.30.8Oct 15, 2026

changedInput schema / properties / comparison_window / description

Previous value: -"Baseline window to compare against. `\"auto\"` (default) averages three offsets (1×, 2×, 3× the timeRange) for noise smoothing. A specific offset like `\"7d\"` compares to that single anchor — e.g. `{timeRange: \"1d\", comparison_window: \"1d\"}` = today vs yesterday (deploy-delta); `{timeRange: \"7d\", comparison_window: \"7d\"}` = this week vs last week."New value: +"Baseline window to compare against. `\"auto\"` (default) averages three offsets (1×, 2×, 3× the timeRange) for noise smoothing. A specific offset like `\"7d\"` compares to that single anchor: e.g. `{timeRange: \"1d\", comparison_window: \"1d\"}` = today vs yesterday (deploy-delta); `{timeRange: \"7d\", comparison_window: \"7d\"}` = this week vs last week."

changedInput schema / properties / timeRange / description

Previous value: -"Current window to evaluate. Day-level only — delta math requires day-aligned baseline offsets. For sub-day spike investigation use `log10x_pattern_trend` or `log10x_investigate`."New value: +"Current window to evaluate. Day-level only: delta math requires day-aligned baseline offsets. For sub-day spike investigation use `log10x_pattern_trend` or `log10x_investigate`."

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?

Beyond the readOnly/idempotent/openWorld annotations, the description discloses real behavior: noise-level deltas are dropped by gates, brand-new patterns are EXCLUDED and shunted elsewhere, and each returned row carries delta_usd/baseline_usd/current_usd/delta_pct plus a gate-crossed flag. It does not contradict the annotations; it mainly stops short of describing pagination/ordering beyond `limit`.

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?

Dense but front-loaded: the core ranking semantics and sibling distinction come first, then gates, then window semantics, then use cases. Slightly long with some duplication of the schema's window examples, but nearly every sentence carries routing or behavioral value.

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?

For a 10-param, 0-required read tool with an output schema and safety annotations, the description covers the decision-relevant gaps: what it ranks, how it differs from siblings, gating behavior, and where excluded patterns go. Nothing an agent needs to call it correctly 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 ten parameters are already documented. The description's treatment of `comparison_window` (auto = averaged offsets vs single anchor) and `timeRange` is nearly verbatim from the schema, so it adds little beyond repetition. 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?

States a specific verb+resource with a precise ranking semantics: patterns ranked by delta vs a baseline window. It explicitly distinguishes itself from `log10x_top_patterns` (ranks by current cost) and `log10x_whats_new` (brand-new patterns), so an agent can pick it apart from siblings without opening a 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?

Names concrete when-to-use triggers ("what grew most this week", "which patterns regressed after the deploy", "what's driving cost up since yesterday") and routes excluded cases explicitly to `log10x_whats_new`, plus sub-day work to `log10x_pattern_trend`/`log10x_investigate` via the schema. Both positive and negative routing are covered.

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

Deploy Server