Skip to main content
Glama
yangkyeongmo

MCP Server for Apache Airflow

by yangkyeongmo

get_health

Check Apache Airflow instance status and system health to monitor operational state and ensure proper functionality.

Instructions

Get instance status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'get_health' tool. It retrieves the health status from the Airflow monitoring API and formats it 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()))]
  • Module-level registration function that includes the 'get_health' tool in a list of functions to be registered with the MCP server.
    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),
        ]
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 implies a read-only operation ('Get'), but doesn't disclose behavioral traits such as authentication needs, rate limits, error conditions, or what 'status' entails (e.g., uptime, metrics, alerts). For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 ('Get instance status') with no wasted words, making it easy to parse. It's front-loaded with the core action and resource, though its brevity contributes to vagueness in other dimensions.

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 minimal but insufficient. It lacks context about what 'instance status' means, how it differs from other get_* tools, and what the output might contain. With no annotations or output schema, more detail is needed to make it complete for effective use.

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 semantics, but that's appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without introducing confusion.

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

Purpose3/5

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

The description 'Get instance status' clearly indicates a read operation ('Get') on a resource ('instance status'), but it's vague about what 'instance' refers to in this context. It doesn't distinguish this tool from siblings like get_config, get_version, or get_health (if present), leaving ambiguity about what specific status information is retrieved.

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 many sibling tools (e.g., get_config, get_version, get_dag_stats), the description lacks context about whether this is for overall system health, specific component status, or other purposes, offering no help in tool selection.

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/yangkyeongmo/mcp-server-apache-airflow'

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