Skip to main content
Glama
log-10x

Log10x MCP Server

Official

Top patterns

log10x_top_patterns
Read-onlyIdempotent

Rank log patterns by byte volume and cost over a time range, per service or all, to find expensive or noisy events, with trajectory badges.

Instructions

Rank log patterns by byte volume and cost per pattern (bytes priced at the destination's $/GB rate when one is set), over a time range, for one service or all. Each row carries a trajectory badge (NEW, ACUTE, GROWING, STABLE or SHRINKING) read against 7, 14 and 21 day baselines. Use for "what is expensive right now", "what are the noisy patterns in this hour", "give me a snapshot of my loudest events". For "what changed this week" or "did the deploy add cost", use log10x_whats_changing, which ranks patterns by change against a comparison_window baseline. Can be scoped by service label. timeRange accepts free-form <n><m|h|d> durations (e.g., 48h, 3d, 15m): there's no enum snap. Pass include to choose which cohort to rank: kept (default, what the Receiver forwarded), dropped (the offloaded / overflow cohort alone), or both (total ingest pre-receiver). Use dropped for "what is the receiver throwing away" and both for an apples-to-apples pre/post comparison. Accepts siem_lens (what-if destination): keeps the measured volumes, prices + gates for that destination at list rates, and stamps siem_actual vs siem_lens in the envelope. REQUIRES Reporter-tier metrics. Before anything is deployed, the POC tools answer the same question from the user's own logs.

Input Schema

NameRequiredDescriptionDefault
viewNoOutput format. Always "summary": the structured JSON envelope with patterns, incidents, totals, and chained-tool action hints. Field retained for backward-compat with callers that still pass `view: "summary"`.summary
limitNoNumber of patterns to return. Default 10.
offsetNoSkip the first N patterns of the ranked result (for pagination). Default 0.
includeNoWhich engine-decision cohort to scope to. `kept` (default) = events the engine forwarded as-is (routeState!="drop"): the pre-PL-12 behavior. `dropped` = events stamped routeState="drop" by the engine (the offload/down-tier cohort). `both` = the pre-decision union; per-row output adds kept_bytes / dropped_bytes / dropped_share_pct. Use `dropped` to verify post-deploy realised savings or to answer "which patterns are we offloading right now". Use `both` to compute the offload share denominator in a single call.kept
serviceNoService name to scope the result. Omit for all services.
verboseNoWhen true, every card carries the full forwarder snippet inline, every CTA renders unconditionally, and the volume-trend chart shows on every top-3 card. Default: compact mode (snippet templated once at top, CTAs gated to where they earn their line, chart only on ACUTE/NEW patterns).
severityNoSeverity level to scope the result (e.g., `ERROR`, `CRITICAL`, `DEBUG`).
siemScopeNoIgnored: the summary envelope carries no verbatim sample line. Accepted so existing callers still validate.
siem_lensNoWhat-if destination lens: keep the measured volumes, price the $/mo columns at this destination's default rates (env-configured rates never cross destinations). Envelope stamps siem_actual vs siem_lens.
timeRangeNoTime range to aggregate over. Default 1h.1h
environmentNoEnvironment nickname (for multi-env setups).
analyzerCostNoDEPRECATED: use effective_ingest_per_gb. stack ingestion cost in $/GB. Auto-detected from profile if omitted.
include_chartNoSet include_chart=true to embed the rendered chart inline (large; default false to avoid response truncation).
monthly_volume_gbNoWhat-if volume lens (forecast mode): model the environment at THIS monthly volume (decimal GB/month) instead of its measured volume. The real per-pattern shares and pattern mix are held fixed; only absolute bytes and dollars scale, by one uniform factor. Use it to project a prospect onto their own scale, or to forecast a real env after growth. Pairs with siem_lens. This is a PROJECTION: the envelope stamps volume_actual_gb vs volume_projected_gb and the scale factor, and the note points at the POC for the caller real patterns.
effective_ingest_per_gbNoCustomer-supplied $/GB rate used for the dollar overlay. When set, headline tags `rate_source=customer_supplied`. When absent, falls back to the destination default rate (`rate_source=list_price`; a list price only where the vendor sells logs per GB) or omits dollars entirely (`rate_source=unset`).

Output Schema

NameRequiredDescriptionDefault
dataNo
toolYes
viewNosummary
imagesNo
actionsNo
summaryYes
warningsNo
truncatedNo
next_cursorNo
render_hintNo
generated_atYes
schema_epochYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.30.8
    • changedInput schema / properties / analyzerCost / description
      Previous value: -"DEPRECATED — use effective_ingest_per_gb. stack ingestion cost in $/GB. Auto-detected from profile if omitted."New value: +"DEPRECATED: use effective_ingest_per_gb. stack ingestion cost in $/GB. Auto-detected from profile if omitted."
    • changedInput schema / properties / effective_ingest_per_gb / description
      Previous value: -"Customer-supplied $/GB rate used for the dollar overlay. When set, headline tags `rate_source=customer_supplied`. When absent, falls back to the profile list rate (`rate_source=list_price`) or omits dollars entirely (`rate_source=unset`)."New value: +"Customer-supplied $/GB rate used for the dollar overlay. When set, headline tags `rate_source=customer_supplied`. When absent, falls back to the destination default rate (`rate_source=list_price`; a list price only where the vendor sells logs per GB) or omits dollars entirely (`rate_source=unset`)."
    • changedInput schema / properties / include / description
      Previous value: -"Which engine-decision cohort to scope to. `kept` (default) = events the engine forwarded as-is (routeState!=\"drop\") — the pre-PL-12 behavior. `dropped` = events stamped routeState=\"drop\" by the engine (the offload/down-tier cohort). `both` = the pre-decision union; per-row output adds kept_bytes / dropped_bytes / dropped_share_pct. Use `dropped` to verify post-deploy realised savings or to answer \"which patterns are we offloading right now\". Use `both` to compute the offload share denominator in a single call."New value: +"Which engine-decision cohort to scope to. `kept` (default) = events the engine forwarded as-is (routeState!=\"drop\"): the pre-PL-12 behavior. `dropped` = events stamped routeState=\"drop\" by the engine (the offload/down-tier cohort). `both` = the pre-decision union; per-row output adds kept_bytes / dropped_bytes / dropped_share_pct. Use `dropped` to verify post-deploy realised savings or to answer \"which patterns are we offloading right now\". Use `both` to compute the offload share denominator in a single call."
    • changedInput schema / properties / siemScope / description
      Previous value: -"stack scope for the verbatim sample line on the top rows."New value: +"Ignored: the summary envelope carries no verbatim sample line. Accepted so existing callers still validate."
    • changedInput schema / properties / siem_lens / description
      Previous value: -"What-if destination lens: keep the real volumes, price the $/mo columns at this destination's list rates (env-configured rates never cross destinations). Envelope stamps siem_actual vs siem_lens."New value: +"What-if destination lens: keep the measured volumes, price the $/mo columns at this destination's default rates (env-configured rates never cross destinations). Envelope stamps siem_actual vs siem_lens."
    • changedInput schema / properties / view / description
      Previous value: -"Output format. Always \"summary\" — the structured JSON envelope with patterns, incidents, totals, and chained-tool action hints. Field retained for backward-compat with callers that still pass `view: \"summary\"`."New value: +"Output format. Always \"summary\": the structured JSON envelope with patterns, incidents, totals, and chained-tool action hints. Field retained for backward-compat with callers that still pass `view: \"summary\"`."
  2. First observedv1.30.7

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), but the description adds substantive behavior beyond them: the Reporter-tier metrics requirement, the siem_lens keep-volumes/price-at-destination behavior and siem_actual vs siem_lens envelope stamping, and the POC-tools fallback before deployment. These are real operational constraints not present in annotations.

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 with the purpose then routing, cohort, and lens guidance in logical order. It is dense and long, with a few clauses that restate schema descriptions (timeRange format appears in both), 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?

Output schema exists so return values needn't be explained. Given 15 parameters and the multi-mode nature (cost ranking, cohort scoping, siem lens, volume projection), the description covers the decision-relevant context, prerequisites, and alternatives thoroughly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds interpretive value beyond the schema: it explains the intent behind include=kept/dropped/both (e.g., use `dropped` for 'what is the receiver throwing away', `both` for a pre/post comparison) and clarifies that timeRange has no enum snap. Some text duplicates schema wording, holding it below 5.

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 and resource (rank log patterns by byte volume and cost), the scope (time range, one service or all), and explicitly names the sibling it is not (log10x_whats_changing) with the condition that selects it. An agent can disambiguate from siblings without opening either 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?

Provides explicit when-to-use examples ('what is expensive right now', 'noisy patterns this hour'), an explicit when-not with the named alternative (log10x_whats_changing for 'what changed this week'/'did the deploy add cost'), plus cohort-selection guidance for include=kept/dropped/both and the siem_lens what-if path.

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