Skip to main content
Glama

get_event_log

Retrieve specific event log entries from Apache Airflow clusters to monitor workflow execution and troubleshoot issues.

Instructions

[Tool Role]: Retrieves a specific event log entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_log_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_event_log' tool. It makes a GET request to the Airflow API endpoint /eventLogs/{event_log_id} to retrieve the specific event log entry and returns the JSON response.
    async def get_event_log(event_log_id: int) -> Dict[str, Any]:
        """[Tool Role]: Retrieves a specific event log entry."""
        resp = await airflow_request("GET", f"/eventLogs/{event_log_id}")
        resp.raise_for_status()
        return resp.json()
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. It states the tool retrieves an entry, implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or what happens if the ID doesn't exist. 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 and front-loaded, consisting of a single, clear sentence that directly states the tool's role. There is no wasted verbiage or unnecessary elaboration, making it efficient for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and 0% schema description coverage, it lacks details on parameter semantics and behavioral traits, leaving room for improvement in completeness.

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?

Schema description coverage is 0%, meaning the parameter 'event_log_id' is undocumented in the schema. The description adds no semantic information about this parameter, such as what constitutes a valid ID, where to find it, or its format. With one required parameter and no schema descriptions, the description fails to compensate for this gap.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Retrieves') and resource ('a specific event log entry'), making it immediately understandable. However, it doesn't distinguish this from sibling tools like 'list_event_logs' or 'get_event_logs' (if they existed), which would require explicit differentiation for a perfect score.

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. It doesn't mention sibling tools like 'list_event_logs' for listing multiple entries or specify prerequisites such as needing an event_log_id. Without this context, the agent must infer usage from the tool name alone.

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/call518/MCP-Airflow-API'

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