Skip to main content
Glama

list_config_sections

Retrieve all configuration sections with summaries to monitor and manage Apache Airflow clusters without API complexity.

Instructions

[Tool Role]: Lists all configuration sections with summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_config_sections' tool. It fetches the Airflow configuration via the API, summarizes the sections with option counts and sample option names, and handles access errors.
    async def list_config_sections() -> Dict[str, Any]:
        """[Tool Role]: Lists all configuration sections with summary."""
        try:
            resp = await airflow_request("GET", "/config")
            resp.raise_for_status()
            config_data = resp.json()
            
            sections_summary = {}
            for section_name, section_data in config_data.get("sections", {}).items():
                options_count = len(section_data.get("options", {}))
                sections_summary[section_name] = {
                    "options_count": options_count,
                    "sample_options": list(section_data.get("options", {}).keys())[:5]
                }
            
            return {
                "sections_summary": sections_summary,
                "total_sections": len(sections_summary)
            }
        except Exception as e:
            return {
                "error": f"Configuration access denied: {str(e)}",
                "note": "This requires 'expose_config = True' in airflow.cfg [webserver] section"
            }
  • Calls register_common_tools(mcp) which registers the list_config_sections tool (among others) for Airflow API v1.
    common_tools.register_common_tools(mcp)
  • Calls register_common_tools(mcp) which registers the list_config_sections tool (among others) for Airflow API v2.
    common_tools.register_common_tools(mcp)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'Lists all configuration sections with summary,' implying a read-only operation, but doesn't disclose behavioral traits like pagination, rate limits, permissions required, or what 'summary' entails. This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence that front-loads the core functionality ('Lists all configuration sections with summary'). There's no wasted text, making it highly concise and well-structured.

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

Completeness3/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, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and siblings that might overlap, it lacks completeness in behavioral context and usage differentiation, leaving room for improvement.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, earning a baseline score for tools with no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Lists') and resource ('all configuration sections with summary'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_config' or 'search_config_options', which likely have overlapping functionality with configuration data.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_config' and 'search_config_options' that might handle configuration data differently, the description lacks any context about use cases, 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/call518/MCP-Airflow-API'

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