Log10x MCP Server

Official

by log-10x

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Cost reduction options

log10x_cost_options

Read-onlyIdempotent

Return the capability-gated log cost-cutting menu for the chosen SIEM: six modes (drop, sample, compact, tier_down, offload, observe_only) or two on Reporter/Dev, then route the pick.

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 real volumes, prices + gates for that destination at list rates, and stamps siem_actual vs siem_lens in the envelope.

Input Schema

TableJSON 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

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.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/open-world, but the description adds substantive behavior beyond them: tier-dependent menu collapse (6 vs 2 entries), capability gating by receiver tier/SIEM/offload bucket, and envelope semantics (must_render_verbatim, must_ask_user, forbidden_next_actions). These are non-obvious operational traits an agent needs.

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 trigger condition and packed with routing rules; every sentence conveys operational detail. It is dense rather than bloated, though some clauses overlap with the schema descriptions, preventing a 5.

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 menu-generating routing tool with an output schema present, the description supplies everything needed: entry conditions, tier-dependent output, envelope fields, and downstream routing. Nothing material 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 the schema carries the parameter burden, and the description largely restates it (e.g., siem_lens provenance stamping and destination forwarding are already in the schema). It adds narrative value by explaining how parameters survive the hop into routes_to.args, but this is marginal over the schema text, so baseline 3 applies.

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 names a specific action (return the cost-reduction option menu) and clearly distinguishes it from siblings by stating it produces a mode menu that routes to log10x_explain_mode rather than performing the estimation itself. It also specifies tier-dependent output shape (6-mode vs 2-entry), making the tool's identity unmistakable.

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?

Explicitly states the trigger condition ('CALL THIS after the user picks ... from log10x_start') and the downstream routing ('All non-observe modes route to log10x_explain_mode'). It also names forbidden next actions (do not call estimate_savings, configure_engine, or pattern_mitigate until the user picks), which is unusually precise guidance.

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

Deploy Server