Log10x MCP Server

Official

by log-10x

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Discover env (k8s + AWS)

log10x_discover_env

Read-onlyIdempotent

Read-only discovery of Kubernetes and AWS infrastructure to detect log forwarders, installed Log10x apps, and metrics backends. Pre-install step for Log10x; returns a snapshot for advisor tools.

Instructions

Read-only discovery of the caller's Kubernetes cluster + AWS account — i.e. the customer's INFRASTRUCTURE environment, NOT their Log10x account. When the user wants to install Log10x: call this tool FIRST and then log10x_advise_install — that's the whole pre-flight. Do NOT call log10x_doctor / log10x_login_status / log10x_savings / etc. before the install; the wizard handles all login + license logic internally, and surfacing those tools' optional-capability warnings (Retriever, Datadog backfill, cross-pillar metrics) makes the install feel more complicated than it is. Probes kubectl (workloads, DaemonSets, Helm releases, service-account IRSA annotations, metrics-backend agents) and AWS (EKS, S3, SQS, CloudWatch log groups) to detect: which forwarder is running (Fluent Bit, Fluentd, Filebeat, Logstash, OTel Collector, Vector), which log10x apps are already installed (Reporter, Receiver, Retriever), and which metrics backends are already deployed (Datadog Agent, Prometheus, Elastic, CloudWatch Agent, etc.). Returns a terse markdown report + a snapshot_id (cached 30 min) the advisor tools consume. Do NOT call this tool to answer "which Log10x environments do I have access to" / "list my envs" / "switch envs" — those are about the user's Log10x ACCOUNT environments, use log10x_login_status for that. Call THIS tool only when the question is about k8s workloads, AWS infra, or "what's deployed in my cluster". Every shell call is logged in the snapshot's probeLog for audit. No writes, no state mutation: only kubectl get and aws ... describe/list verbs. Tier prerequisites: none — this is a pre-install tool and runs against any customer environment.

Input Schema

TableJSON Schema

Name	Required	Description
`region`	No	AWS region to probe. If omitted, uses the region from your AWS CLI profile.
`skip_aws`	No	Skip all AWS probes (for cluster-only discovery).
`namespaces`	No	Explicit list of Kubernetes namespaces to probe. If omitted, the tool auto-picks up to 5 likely candidates (demo, logging, observability, otel-demo, default) plus kube-system.
`bucket_hint`	No	Substring to match against S3 bucket names. Defaults to "retriever"; also matches "log10x" and "tenx" out of the box.
`skip_kubectl`	No	Skip all kubectl probes (for AWS-only discovery or when cluster access is restricted).
`forwarder_hint`	No	Override forwarder detection. Use this if multiple forwarders are running and you want the advisor to target a specific one.
`namespace_hint`	No	Preferred namespace for new installs. Defaults to "logging" unless an existing forwarder namespace is found.
`eks_cluster_name`	No	EKS cluster to describe. If omitted and exactly one cluster exists in the account/region, that one is auto-selected.

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?

Beyond the readOnlyHint/idempotentHint annotations, the description discloses what is probed (kubectl workloads, IRSA annotations, AWS EKS/S3/SQS/CloudWatch), that shell calls are logged in probeLog for audit, that only get/describe/list verbs are used, a 30-min cache producing snapshot_id, and that no tier prerequisites apply. This is substantial context the annotations alone do not convey.

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?

Long but front-loaded and information-dense: the core purpose leads, followed by when-to-use, when-not-to-use, then capabilities. The bolding aids scanning, though some routing detail is repeated across the middle section, keeping it just short of maximally tight.

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?

An output schema exists, so return values need no exposition. For a zero-required-param discovery tool the description covers purpose, routing, safety profile, caching, and audit behavior — everything an agent needs to invoke it correctly.

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 eight parameters are already documented with defaults and semantics. The description adds no per-parameter syntax or override guidance beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 (read-only discovery/probe) and resource (caller's Kubernetes cluster + AWS account infrastructure), and explicitly disambiguates from the similarly-named Log10x ACCOUNT environment concept. An agent can tell it apart from log10x_login_status 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?

Gives explicit routing: call FIRST when the user wants to install Log10x, then log10x_advise_install, and explicitly names tools NOT to call beforehand (log10x_doctor, log10x_login_status, log10x_savings). Also names the alternative for account-env questions. Nothing is left to inference.

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

Deploy Server