Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_config

Retrieve current Apache Airflow configuration settings to manage deployment parameters and system behavior.

Instructions

Get current configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNo

Implementation Reference

  • The main handler function for the 'get_config' tool. It accepts an optional 'section' parameter, calls the Airflow ConfigApi.get_config, and returns the response as TextContent.
    async def get_config(
        section: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        # Build parameters dictionary
        kwargs: Dict[str, Any] = {}
        if section is not None:
            kwargs["section"] = section
    
        response = config_api.get_config(**kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The get_all_functions utility that provides the registration tuple for 'get_config', which is later used by main.py to register the tool via app.add_tool.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_config, "get_config", "Get current configuration", True),
            (get_value, "get_value", "Get a specific option from configuration", True),
        ]
  • src/main.py:23-23 (registration)
    Mapping of APIType.CONFIG to the get_config_functions (aliased get_all_functions from config.py), used to dynamically load and register config tools.
    APIType.CONFIG: get_config_functions,
  • src/main.py:91-91 (registration)
    The app.add_tool call that registers the 'get_config' handler (along with others) into the MCP server.
    app.add_tool(func, name=name, description=description)
Behavior1/5

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

No annotations are provided, so the description carries full burden but offers no behavioral details. It doesn't disclose if this is a read-only operation, requires permissions, has side effects, or involves rate limits. The vague 'Get' implies retrieval but lacks transparency on safety or constraints.

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 with a single sentence, 'Get current configuration', which is front-loaded and wastes no words. However, this brevity comes at the cost of under-specification, but it earns full marks for conciseness as every word serves a purpose.

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

Completeness1/5

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

Given no annotations, 0% schema coverage, no output schema, and a vague purpose, the description is incomplete. It fails to compensate for missing structured data, leaving the agent without necessary context for a tool that likely retrieves system or application settings.

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

Parameters1/5

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

The input schema has 1 parameter with 0% description coverage, and the tool description adds no parameter information. It doesn't explain what 'section' means, its format, or how it affects the retrieval, leaving the parameter undocumented and unclear.

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

Purpose2/5

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

The description 'Get current configuration' restates the tool name 'get_config' with minimal elaboration, making it tautological. It specifies the verb 'Get' and resource 'configuration' but lacks detail on what configuration entails or scope, failing to distinguish it from sibling tools like get_variable or get_connection.

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

Usage Guidelines1/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 many sibling tools for retrieving specific resources (e.g., get_variable, get_connection), the description offers no context, prerequisites, or exclusions, leaving the agent without direction.

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/nikhil-ganage/mcp-server-airflow-token'

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