Skip to main content
Glama

ako_config_show

Read-onlyIdempotent

Display current AKO Helm values.yaml configuration, including controller IP, cloud name, network settings, and feature flags.

Instructions

[READ] Show current AKO Helm values.yaml configuration — controller IP, cloud name, network settings, and feature flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler: runs 'helm get values ako -n avi-system -o yaml' to fetch current AKO Helm values.yaml configuration.
    def show_ako_config(namespace: str = "avi-system") -> None:
        """Show current AKO Helm values."""
        result = subprocess.run(
            ["helm", "get", "values", "ako", "-n", namespace, "-o", "yaml"],
            capture_output=True,
            text=True,
            timeout=120,
        )
        if result.returncode != 0:
            console.print(f"[red]Failed to get AKO values: {result.stderr.strip()}[/red]")
            raise SystemExit(1)
    
        console.print("\n[bold]AKO Helm Values[/bold]\n")
        console.print(result.stdout)
  • MCP tool def: ako_config_show() decorated with @mcp.tool and @vmware_tool, imports show_ako_config and captures its output.
    def ako_config_show() -> str:
        """[READ] Show current AKO Helm values.yaml configuration — controller IP, cloud name, network settings, and feature flags."""
        from vmware_avi.ops.ako_config import show_ako_config
        return _capture_output(show_ako_config)
  • Registration: decorated with @mcp.tool and @vmware_tool(risk_level='low') registering the tool named 'ako_config_show' with FastMCP.
    @mcp.tool(annotations={"readOnlyHint": True, "destructiveHint": False, "idempotentHint": True, "openWorldHint": True})
    @vmware_tool(risk_level="low")
    def ako_config_show() -> str:
        """[READ] Show current AKO Helm values.yaml configuration — controller IP, cloud name, network settings, and feature flags."""
        from vmware_avi.ops.ako_config import show_ako_config
        return _capture_output(show_ako_config)
  • Schema: annotations={'readOnlyHint': True, 'destructiveHint': False, 'idempotentHint': True, 'openWorldHint': True} — read-only, no params, returns str.
    def ako_config_show() -> str:
        """[READ] Show current AKO Helm values.yaml configuration — controller IP, cloud name, network settings, and feature flags."""
        from vmware_avi.ops.ako_config import show_ako_config
        return _capture_output(show_ako_config)
  • Helper: _capture_output() runs a function and captures Rich console output as plain text, used to wrap show_ako_config.
    def _capture_output(func, *args, **kwargs) -> str:
        """Run a function and capture its Rich console output as plain text."""
        import importlib  # noqa: F401 — used via sys.modules lookup
        import sys
    
        buf = StringIO()
        from rich.console import Console
        capture_console = Console(file=buf, force_terminal=False, width=120)
    
        mod_name = func.__module__
        mod = sys.modules.get(mod_name)
        original_console = getattr(mod, "console", None) if mod else None
    
        if mod and original_console is not None:
            mod.console = capture_console
    
        try:
            func(*args, **kwargs)
        except SystemExit:
            pass
        finally:
            if mod and original_console is not None:
                mod.console = original_console
    
        return buf.getvalue()
Behavior3/5

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

Annotations already mark the tool as readOnlyHint: true, destructiveHint: false, and idempotentHint: true. The description adds minimal behavioral context beyond what annotations provide, only specifying it shows configuration (no side effects). With annotations covering the safety profile, a 3 is appropriate.

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 a single concise sentence that front-loads the purpose with '[READ]' and efficiently communicates what the tool does without any redundant information.

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 has no parameters, annotations fully describe its safety profile, and an output schema exists, the description is complete enough for an agent to understand and invoke this tool correctly.

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?

The tool has zero parameters, so the description does not need to explain parameter semantics. The schema coverage is 100% (no parameters to describe). Baseline is 4 for no-parameter tools.

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 this is a read tool that shows the AKO Helm values.yaml configuration, listing specific details like controller IP, cloud name, network settings, and feature flags. It uses the verb 'Show' and specifies the resource, making the purpose unambiguous.

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 includes '[READ]' to hint at read-only usage but does not explicitly state when to use this tool versus its siblings (e.g., ako_config_diff, ako_sync_status). There is no guidance on prerequisites or alternatives, leaving the agent to infer usage context.

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/zw008/VMware-AVI'

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