Skip to main content
Glama

search_config_options

Search for Apache Airflow configuration options by entering a specific term to find relevant settings.

Instructions

[Tool Role]: Searches for configuration options matching a term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
search_termYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'search_config_options' tool. It fetches the full Airflow config via API, searches for options matching the search_term in names and values, and returns structured matches grouped by config sections.
    @mcp.tool()
    async def search_config_options(search_term: str) -> Dict[str, Any]:
        """[Tool Role]: Searches for configuration options matching a term."""
        try:
            resp = await airflow_request("GET", "/config")
            resp.raise_for_status()
            config_data = resp.json()
            
            matching_options = {}
            for section_name, section_data in config_data.get("sections", {}).items():
                section_matches = {}
                for option_name, option_data in section_data.get("options", {}).items():
                    if search_term.lower() in option_name.lower() or search_term.lower() in str(option_data.get("value", "")).lower():
                        section_matches[option_name] = option_data
                
                if section_matches:
                    matching_options[section_name] = section_matches
            
            return {
                "search_term": search_term,
                "matching_options": matching_options,
                "total_matches": sum(len(section) for section in matching_options.values())
            }
        except Exception as e:
            return {
                "error": f"Configuration access denied: {str(e)}",
                "note": "This requires 'expose_config = True' in airflow.cfg [webserver] section"
            }
  • The @mcp.tool() decorator registers the search_config_options function as an MCP tool within the register_common_tools function.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Searches for') but reveals nothing about permissions, rate limits, pagination, search scope (e.g., global vs. section-specific), or what constitutes a 'match'. For a search tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 extremely concise—a single sentence that directly states the tool's role. There's zero waste or redundancy. It's front-loaded with the core action and efficiently communicates the basic purpose without unnecessary elaboration.

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 an output schema (which handles return values) and only one parameter, the description's minimalism is somewhat acceptable. However, with no annotations and 0% schema coverage, it lacks context about search behavior, permissions, or sibling differentiation. It meets a bare minimum but leaves significant gaps for the agent to navigate.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'matching a term' which hints at the 'search_term' parameter, but provides no semantic context—what type of term (keyword, regex?), case sensitivity, or how matching works. With one undocumented parameter, the description adds minimal value beyond the parameter name itself.

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 tool's purpose with a specific verb ('Searches for') and resource ('configuration options'), and includes a qualifier ('matching a term'). However, it doesn't explicitly differentiate from sibling tools like 'get_config' or 'list_config_sections', which appear to be related configuration tools. The description is functional but lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple configuration-related siblings (e.g., 'get_config', 'list_config_sections', 'get_config_section'), there's no indication of when this search tool is preferred over those retrieval tools. The agent must infer usage from the name alone.

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