Skip to main content
Glama
yangkyeongmo

MCP Server for Apache Airflow

by yangkyeongmo

get_version

Retrieve Apache Airflow version details to verify system compatibility and monitor deployment status.

Instructions

Get version information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for the get_version tool that calls monitoring_api.get_version() and returns the response as TextContent.
    async def get_version() -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Get version information about Airflow.
        """
        response = monitoring_api.get_version()
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registration of the get_version tool within the get_all_functions() that lists available MCP tools.
    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 the full burden of behavioral disclosure. 'Get version information' implies a read-only operation, but it doesn't specify any behavioral traits such as authentication requirements, rate limits, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 just three words, front-loaded with the key action and resource. There is zero waste or redundancy, making it easy to parse quickly. Every word earns its place by directly conveying the tool's purpose without extra fluff.

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 complexity is low (0 parameters, no output schema), the description is minimal but adequate for basic understanding. However, with no annotations and no output schema, it lacks completeness in terms of behavioral context and expected return values. For a tool that might return structured version data, more detail would be helpful, but it's not critically incomplete.

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 schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. This meets the baseline for tools with no parameters, as it avoids unnecessary details.

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 version information' clearly states the verb ('Get') and resource ('version information'), making the purpose understandable. However, it's somewhat vague about what 'version information' specifically entails (e.g., software version, API version, system version) and doesn't differentiate from siblings like 'get_health' or 'get_config', which could also provide system-related information.

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. Given the sibling tools include other informational tools like 'get_health' and 'get_config', the description lacks context on when version information is needed or how it differs from other get operations. This leaves the agent without explicit usage instructions.

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