Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_health

Check the operational status of an Apache Airflow deployment to verify system health and availability for workflow management.

Instructions

Get instance status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that implements the 'get_health' tool logic. It calls the Airflow monitoring API to fetch health status and returns it formatted as MCP TextContent.
    async def get_health() -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Get the status of Airflow's metadatabase, triggerer and scheduler.
        It includes info about metadatabase and last heartbeat of scheduler and triggerer.
        """
        response = monitoring_api.get_health()
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The get_all_functions() function that registers the 'get_health' tool by providing its handler function, name, description, and read-only status, which is later used in main.py to add 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_health, "get_health", "Get instance status", True),
            (get_version, "get_version", "Get version information", True),
        ]
  • Initialization of the monitoring_api client instance used by the get_health handler to query Airflow's health endpoint.
    monitoring_api = MonitoringApi(api_client)
  • src/main.py:90-92 (registration)
    The generic tool registration loop in main.py where functions from get_all_functions() (including get_health) are added to the MCP app using app.add_tool().
    for func, name, description, *_ in functions:
        app.add_tool(func, name=name, description=description)
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. 'Get instance status' implies a read-only operation, but it doesn't disclose behavioral traits like authentication needs, rate limits, what 'status' entails (e.g., uptime, errors), or response format. For a tool with zero annotation coverage, this minimal description leaves critical gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('Get instance status'), which could be efficient, but it's under-specified rather than appropriately sized. It lacks necessary detail to be helpful, so it doesn't earn a high score for conciseness. However, it's not verbose or poorly structured.

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

Completeness2/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is incomplete. It doesn't explain what 'instance status' means, what the return value includes, or how it differs from other get_* tools. With no annotations and no output schema, more context is needed for the agent to use it effectively.

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 there are no parameters to document. The description doesn't need to add parameter semantics, and it doesn't incorrectly mention any. Baseline 4 is appropriate as it avoids misleading parameter information.

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 instance status' restates the tool name 'get_health' in slightly different words (tautology). It doesn't specify what 'instance' refers to or what 'status' includes, making it vague. However, it's not completely missing or misleading, just insufficiently specific.

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. Given the many sibling tools (e.g., get_config, get_version, get_connection), there's no indication of when health status is needed versus other diagnostic or configuration tools. This absence is a significant gap.

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