Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_version

Retrieve version details for Apache Airflow deployments through the MCP server with Bearer token authentication.

Instructions

Get version information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that implements the 'get_version' tool. It retrieves version information from the Airflow MonitoringApi and returns it as formatted text content.
    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()))]
  • The get_all_functions that returns the registration tuple for 'get_version' (and 'get_health'). This function is imported in src/main.py and its output is used to register tools 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),
        ]
  • src/main.py:78-92 (registration)
    The main tool registration loop in src/main.py that calls get_all_functions from monitoring (via APITYPE_TO_FUNCTIONS[APIType.MONITORING]) and registers each tool including 'get_version' using app.add_tool.
    for api in apis:
        logging.debug(f"Adding API: {api}")
        get_function = APITYPE_TO_FUNCTIONS[APIType(api)]
        try:
            functions = get_function()
        except NotImplementedError:
            continue
    
        # Filter functions for read-only mode if requested
        if read_only:
            functions = filter_functions_for_read_only(functions)
    
        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 the full burden of behavioral disclosure. 'Get version information' implies a read-only operation, but it doesn't specify whether this requires authentication, what format the version info is returned in (e.g., string, object), or if there are any rate limits or side effects. 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 'Get version information' is extremely concise—just three words—and front-loaded with the core action. There's no wasted language or unnecessary elaboration, making it easy to parse quickly. Every word earns its place by directly conveying the tool's purpose.

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 has no parameters, no annotations, and no output schema, the description is incomplete for effective use. It doesn't explain what 'version information' entails (e.g., is it a simple string, a JSON object with details?), nor does it provide context on dependencies or errors. For a tool in a server with many sibling tools, more detail is needed to ensure the agent can invoke it correctly without confusion.

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% (since there are no parameters to describe). The description doesn't need to add parameter semantics, and it doesn't incorrectly imply any parameters. A baseline score of 4 is appropriate as the description doesn't mislead about parameters, though it could theoretically mention if version retrieval depends on implicit context (e.g., server vs. client).

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 doesn't specify what system or component's version is being retrieved, nor does it differentiate from similar tools like 'get_health' or 'get_config' that might provide related system information. It's adequate but vague about scope.

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. With sibling tools like 'get_health' (for system health) and 'get_config' (for configuration), there's no indication of whether this tool is for API version, software version, or something else, leaving the agent to guess based on context. No explicit when/when-not or alternative recommendations are given.

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