Skip to main content
Glama
geored

Lumino

by geored
OverviewSchemaRelated ServersScoreDiscussions

live_system_topology_mapper

Generate real-time dependency graphs of Kubernetes and Tekton components to visualize service relationships and resource interconnections for system analysis.

Instructions

Generate real-time dependency graph of Kubernetes/Tekton components and their interconnections.

Maps Services, Deployments, Pipelines, PVCs, and their relationships via ownerReferences and selectors.

Args:
    cluster_names: Clusters to map (default: all).
    component_types: Filter by types (services, deployments, pipelines, pvcs, etc.). Note: secrets are NOT included by default.
    namespace_filter: Regex pattern to filter namespaces.
    depth_limit: Max dependency depth (default: 5).
    include_metrics: Include resource metrics (default: False).
    output_format: "json" (default), "graphviz", or "mermaid".
    skip_on_permission_denied: Continue mapping other resources if permission denied (default: True).

Returns:
    Dict: Topology graph with nodes, edges, summary, metadata, and permission report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cluster_namesNo
component_typesNo
namespace_filterNo
depth_limitNo
include_metricsNo
output_formatNojson
skip_on_permission_deniedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: real-time operation, dependency mapping, permission handling ('skip_on_permission_denied'), and output formats. However, it lacks details on rate limits, authentication requirements, or performance implications.

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 and front-loaded with the core purpose, followed by parameter details and return information. Every sentence earns its place by providing essential information without redundancy, making it efficient and easy to parse.

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?

Given the tool's complexity (7 parameters, no annotations), the description is complete enough. It covers purpose, parameters with semantics, and return values. The presence of an output schema means the description doesn't need to detail return structure, and it adequately addresses the gaps from missing annotations.

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 semantics for all 7 parameters. It explains each parameter's purpose, default values, and important notes (e.g., 'secrets are NOT included by default'), adding 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 tool's purpose with specific verbs ('Generate', 'Maps') and resources ('Kubernetes/Tekton components', 'Services, Deployments, Pipelines, PVCs'), including the mechanism ('via ownerReferences and selectors'). It distinguishes itself from siblings by focusing on real-time dependency graph generation rather than analysis, logging, or resource listing functions.

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

Usage Guidelines3/5

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

The description implies usage for mapping component relationships in Kubernetes/Tekton environments, but does not explicitly state when to use this tool versus alternatives like 'get_kubernetes_resource' or 'pipeline_tracer'. It mentions filtering capabilities but lacks guidance on prerequisites or exclusions.

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-mcp-server'

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