Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_event_log

Retrieve a specific Apache Airflow event log entry by numeric ID to inspect cluster activity and troubleshoot issues.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_log_id": "<event_log_id>"
    },
    "name": "get_event_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_log_idYesNumeric identifier of the event log entry.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / event_log_id / description
      Added value: +"Numeric identifier of the event log entry."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / event_log_id / title
      Removed value: -"Event Log Id"
  5. First observed

TDQS

B3.1/5.0
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 behavioral burden, yet it only says "Retrieves". It does not disclose that this is a read-only, non-mutating operation, nor what happens when the ID does not exist (empty result vs error). An output schema exists, so return values need no explanation, but the operational behavior is essentially undescribed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler and no redundancy. The only dead weight is the "[Tool Role]:" prefix, which conveys nothing to the agent.

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

Completeness4/5

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

For a one-parameter get-by-ID tool with full schema coverage and an output schema, very little needs to be said. The remaining gap is sibling differentiation against list_event_logs, which is a genuine but modest omission.

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

Parameters3/5

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

Schema description coverage is 100%: event_log_id is documented as a numeric identifier and is the only required parameter. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ("Retrieves a specific event log entry"), and the word "specific" vs the sibling list_event_logs implies single-record retrieval. It is clear what the tool does, but it never names the sibling it is distinguished from, which for a family with list_event_logs and all_dag_event_summary would have been easy to add.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named. An agent must infer from the name alone that this is the single-record lookup to use after list_event_logs returns an ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.