Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_config

Retrieve Apache Airflow configuration settings to monitor and manage cluster parameters without API complexity.

Instructions

[Tool Role]: Retrieves Airflow configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_airflow_api/tools/common_tools.py:588-593 (handler)
    The handler function for the 'get_config' tool. Makes a GET request to Airflow's /config endpoint and returns the configuration as JSON.
    @mcp.tool()
async def get_config() -> Dict[str, Any]:
    """[Tool Role]: Retrieves Airflow configuration."""
    resp = await airflow_request("GET", "/config")
    resp.raise_for_status()
    return resp.json()
  • src/mcp_airflow_api/tools/v1_tools.py:23-23 (registration)
    Registration call for v1 tools that includes the get_config tool via common_tools.register_common_tools(mcp)
    common_tools.register_common_tools(mcp)
  • src/mcp_airflow_api/tools/v2_tools.py:24-24 (registration)
    Registration call for v2 tools that includes the get_config tool via common_tools.register_common_tools(mcp)
    common_tools.register_common_tools(mcp)

Tool Definition Quality

B3.2/5.0
Behavior2/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 states the tool retrieves configuration but doesn't specify what 'Airflow configuration' entails (e.g., global settings, environment variables), whether it's a read-only operation, potential rate limits, or the format of the returned data. This leaves significant gaps in understanding the tool's behavior.

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 without any fluff or redundant information. It's front-loaded and wastes no words, making it efficient for quick comprehension.

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 0 parameters, 100% schema coverage, and an output schema exists, the description's minimalism is partially justified. However, for a configuration retrieval tool with no annotations, it should ideally clarify the scope of 'Airflow configuration' (e.g., all settings vs. a subset) and mention that it's a read operation, as the output schema alone might not cover these aspects fully.

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 the input schema has 100% description coverage (though empty), so there's no need for parameter details in the description. The description appropriately avoids discussing parameters, focusing solely on the tool's purpose, which is sufficient given the lack of inputs.

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 ('Retrieves') and resource ('Airflow configuration'), making it immediately understandable. However, it doesn't explicitly differentiate from its sibling 'get_config_section' or 'search_config_options', which handle related configuration tasks, leaving some ambiguity about when to choose this tool over those alternatives.

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 like 'get_config_section' or 'search_config_options'. It lacks context about prerequisites, such as whether authentication is required, or any exclusions, leaving the agent to infer usage from the tool 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