Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_event_logs

Retrieve and filter Airflow event log entries to monitor DAG runs, task executions, and workflow events for debugging and analysis.

Instructions

List log entries from event log

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
order_byNo
dag_idNo
task_idNo
run_idNo
map_indexNo
try_numberNo
eventNo
ownerNo
beforeNo
afterNo
included_eventsNo
excluded_eventsNo

Implementation Reference

  • The main handler function for the 'get_event_logs' tool. It accepts optional filter parameters, builds a kwargs dict, calls the Airflow EventLogApi.get_event_logs, and returns the response as a list containing a TextContent object.
    async def get_event_logs(
        limit: Optional[int] = None,
        offset: Optional[int] = None,
        order_by: Optional[str] = None,
        dag_id: Optional[str] = None,
        task_id: Optional[str] = None,
        run_id: Optional[str] = None,
        map_index: Optional[int] = None,
        try_number: Optional[int] = None,
        event: Optional[str] = None,
        owner: Optional[str] = None,
        before: Optional[datetime] = None,
        after: Optional[datetime] = None,
        included_events: Optional[str] = None,
        excluded_events: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        # Build parameters dictionary
        kwargs: Dict[str, Any] = {}
        if limit is not None:
            kwargs["limit"] = limit
        if offset is not None:
            kwargs["offset"] = offset
        if order_by is not None:
            kwargs["order_by"] = order_by
        if dag_id is not None:
            kwargs["dag_id"] = dag_id
        if task_id is not None:
            kwargs["task_id"] = task_id
        if run_id is not None:
            kwargs["run_id"] = run_id
        if map_index is not None:
            kwargs["map_index"] = map_index
        if try_number is not None:
            kwargs["try_number"] = try_number
        if event is not None:
            kwargs["event"] = event
        if owner is not None:
            kwargs["owner"] = owner
        if before is not None:
            kwargs["before"] = before
        if after is not None:
            kwargs["after"] = after
        if included_events is not None:
            kwargs["included_events"] = included_events
        if excluded_events is not None:
            kwargs["excluded_events"] = excluded_events
    
        response = event_log_api.get_event_logs(**kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Local registration of the 'get_event_logs' tool as part of the list returned by get_all_functions, which provides the function, name, description, and read-only flag.
    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:90-92 (registration)
    Central MCP tool registration loop in main.py where functions from eventlog.get_all_functions (including get_event_logs) are registered by calling app.add_tool with the function, name, and description.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. 'List log entries' implies a read-only operation, but it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the logs are in. The description provides minimal behavioral context beyond the basic operation.

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 at just 6 words. It's front-loaded with the core purpose and contains no unnecessary words or sentences. For such a brief statement, every word earns its place in conveying the basic operation.

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 (14 parameters, no output schema, no annotations), the description is severely incomplete. A listing tool with extensive filtering capabilities needs more context about parameter usage, return format, and behavioral constraints. The minimal description doesn't provide enough information for effective tool selection and invocation.

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?

With 14 parameters and 0% schema description coverage, the description provides no information about any parameters. 'List log entries from event log' doesn't mention filtering capabilities, pagination options (limit/offset), sorting (order_by), or any of the 12 other parameters. The description fails to compensate for the complete lack of schema documentation.

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 'List log entries from event log' clearly states the verb ('List') and resource ('log entries from event log'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_event_log' (singular vs plural), leaving ambiguity about their differences.

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_event_log' (singular) and 'get_dag_dataset_queued_events' available, there's no indication of when this specific listing tool is appropriate versus other event-related tools.

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