Log10x MCP Server

Official

by log-10x

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Cost reduction options

log10x_cost_options

Read-onlyIdempotent

Shows cost-cutting options for logs: returns a capability-gated menu (drop, sample, compact, tier down, offload, observe only) and routes the chosen mode onward.

Instructions

CALL THIS after the user picks 'show me what cutting costs would look like' from log10x_start. At Receiver/Retriever tier returns the 6-mode outcome-first menu (drop / sample / compact / tier_down / offload / observe_only), each gated by the customer's detected capabilities (receiver tier, SIEM type, offload bucket). At Reporter-only or Dev tier, collapses to 2 entries: observe_only + install_receiver (with prose explaining that the full 6-mode menu requires the Receiver in-path). All non-observe modes route to log10x_explain_mode. The envelope carries must_render_verbatim (show to user as-is), must_ask_user (numbered question), and forbidden_next_actions (do not call estimate_savings, configure_engine, or pattern_mitigate until the user picks). 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.

Input Schema

Name	Required	Description
`service`	No	Scope to a service. Passed forward to estimate_savings when the user picks a mode.
`siem_lens`	No	What-if destination lens (alias of `destination` with provenance stamping): gate the 6-mode menu and downstream pricing for THIS destination while the connected pipeline keeps its actual one. The envelope stamps siem_actual vs siem_lens so receipts show the lens.
`destination`	No	Destination stack. When set, routes_to.args carries THIS destination forward to estimate_savings: overrides the env-auto-detected SIEM. Pass when the upstream tool (baseline / configure_engine) already established a destination that differs from the env default; without it, cost_options falls back to siem_detected and routes_to may carry a destination the upstream chain did not pick.
`pattern_hash`	No	Optional pattern hash to scope the cost option menu to a single pattern. When present, routes_to.args will include a proposed_config row for this hash.
`target_percent`	No	% reduction goal carried from log10x_start pick, pre-filled when the user stated a target.
`monthly_volume_gb`	No	What-if volume lens (forecast mode), forwarded to the estimate_savings this menu routes to. cost_options scales nothing itself; it carries this value into routes_to.args so the projection survives the hop. See log10x_estimate_savings for the projection semantics.

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.

Changed1 schema field changedv1.30.8Oct 15, 2026

changedInput schema / properties / destination / description

Previous value: -"Destination stack. When set, routes_to.args carries THIS destination forward to estimate_savings — overrides the env-auto-detected SIEM. Pass when the upstream tool (baseline / configure_engine) already established a destination that differs from the env default; without it, cost_options falls back to siem_detected and routes_to may carry a destination the upstream chain did not pick."New value: +"Destination stack. When set, routes_to.args carries THIS destination forward to estimate_savings: overrides the env-auto-detected SIEM. Pass when the upstream tool (baseline / configure_engine) already established a destination that differs from the env default; without it, cost_options falls back to siem_detected and routes_to may carry a destination the upstream chain did not pick."

First observedv1.30.7Sep 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover read-only/idempotent/open-world, but the description adds substantial behavioral context beyond them: capability gating (receiver tier, SIEM type, offload bucket), the non-observe routing to log10x_explain_mode, the envelope contract (must_render_verbatim, must_ask_user, forbidden_next_actions), and siem_lens provenance stamping (siem_actual vs siem_lens). None of this is in the 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?

A dense, front-loaded block with no filler sentences – every clause (tier variants, routing, envelope, lens) carries operational weight. It runs long, but the length is justified by the branching behavior; slightly tighter grouping of the envelope and lens clauses would read better.

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?

Complete for a branching menu tool: entry condition, tier-dependent output shapes, downstream routing, envelope fields, and forbidden actions are all present, and an output schema exists so return-value enumeration is unnecessary. Nothing an agent needs to call it correctly is omitted.

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 meaningfully amplifies it: siem_lens is framed as a what-if lens that keeps measured volumes but re-gates and re-prices at list rates for the lens destination, and destination is described as an override of env-autodetected SIEM carried forward in routes_to.args. That is semantics the schema text alone implies but does not spell out.

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 resource (the cost-reduction option menu) with tier-conditional content, and explicitly distinguishes itself from siblings by naming log10x_start as the trigger and log10x_explain_mode / log10x_estimate_savings / configure_engine / pattern_mitigate as downstream or forbidden tools. An agent can place this tool in the flow 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?

Explicit when-to-use ('CALL THIS after the user picks show me what cutting costs would look like from log10x_start'), variant behavior per tier (6-mode menu at Receiver/Retriever, 2-entry collapse at Reporter-only/Dev), and explicit exclusions ('forbidden_next_actions ... do not call estimate_savings, configure_engine, or pattern_mitigate until the user picks').

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

Deploy Server