Skip to main content
Glama
geored

Lumino

check_cluster_certificate_health

Scan TLS secrets and system certificates across clusters to detect expiring certificates, prevent service disruptions, and provide renewal recommendations with customizable thresholds.

Instructions

Scan for expiring certificates across the cluster to prevent service disruptions.

Scans TLS secrets, system certificates, and provides renewal recommendations.

Args:
    warning_threshold_days: Days before expiration for warning (default: 30).
    critical_threshold_days: Days before expiration for critical alert (default: 7).
    include_system_certs: Include system certificates (default: True).
    include_user_certs: Include user certificates (default: True).
    namespaces: Namespaces to scan (default: all accessible).
    certificate_types: Types to check: "tls", "ca", "client", "server" (default: all).

Returns:
    Dict: Certificate health with expiration timeline, recommendations, and security findings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
warning_threshold_daysNo
critical_threshold_daysNo
include_system_certsNo
include_user_certsNo
namespacesNo
certificate_typesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses what gets scanned (TLS secrets, system certificates) and that it provides renewal recommendations, but doesn't mention permissions needed, rate limits, whether it's read-only or has side effects, or how it handles large clusters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with purpose statement, scope clarification, and organized parameter documentation. Every sentence earns its place, and information is front-loaded with the core purpose first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters with no schema descriptions and an output schema present, the description does an excellent job explaining parameters and return format. However, for a cluster scanning tool with no annotations, it could better address behavioral aspects like performance implications or authorization requirements.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing clear semantic explanations for all 6 parameters, including default values, valid options for certificate_types, and the meaning of each threshold. This adds significant value beyond the bare schema.

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 clearly states the specific action ('scan for expiring certificates'), resource ('across the cluster'), and purpose ('to prevent service disruptions'). It distinguishes from siblings by focusing on certificate health rather than logs, events, or other resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (preventing service disruptions) but doesn't explicitly state when to use this tool versus alternatives like 'investigate_tls_certificate_issues' or other diagnostic tools. It provides clear purpose but lacks explicit sibling differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/geored/Lumino'

If you have feedback or need assistance with the MCP directory API, please join our Discord server