Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_event_log

Retrieve specific Airflow event log entries by ID to monitor workflow execution details and troubleshoot pipeline issues.

Instructions

Get a specific log entry by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_log_idYes

Implementation Reference

  • The main handler function for the 'get_event_log' tool. It takes an event_log_id, calls the Airflow EventLogApi, and returns the response as text content.
    async def get_event_log(
        event_log_id: int,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = event_log_api.get_event_log(event_log_id=event_log_id)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Module-level registration function that includes the 'get_event_log' tool in the list for MCP server registration.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_event_logs, "get_event_logs", "List log entries from event log", True),
            (get_event_log, "get_event_log", "Get a specific log entry by ID", True),
        ]
  • src/main.py:79-92 (registration)
    Top-level registration loop in main.py that imports and adds 'get_event_log' via get_eventlog_functions() and app.add_tool.
    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. It states it 'gets' a log entry, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling (e.g., what happens if the ID doesn't exist), or return format. This is a significant gap for a tool with no annotation coverage.

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 a single, clear sentence with zero waste. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 no annotations, 0% schema coverage, no output schema, and a sibling tool ('get_event_logs'), the description is incomplete. It doesn't explain the return values, error cases, or how it differs from similar tools, leaving gaps for the agent to infer behavior in a complex environment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions 'by ID', which aligns with the single parameter 'event_log_id', but schema description coverage is 0%, so the schema provides no details about the parameter. The description adds minimal meaning (it's an ID) but doesn't specify format, constraints, or examples, failing to compensate for the low coverage.

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 a specific log entry by ID' clearly states the action (get) and resource (log entry), but it's vague about what kind of log entry (event log) and doesn't distinguish it from sibling tools like 'get_event_logs' (plural) or other get_* tools. It's functional but lacks specificity.

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. For example, it doesn't mention when to use 'get_event_log' (by ID) versus 'get_event_logs' (list) or other retrieval tools like 'get_dag_run'. The description assumes the agent knows the context without explicit 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/nikhil-ganage/mcp-server-airflow-token'

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