Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_dataset_events

Retrieve events for a specific dataset URI from Airflow's v1 API to track dataset activity and dependencies.

Instructions

[Tool Role]: Gets events for a specific dataset (v1 API only - v2 uses Assets).

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": {
      "dataset_uri": "<dataset_uri>"
    },
    "name": "get_dataset_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 20.
offsetNoNumber of records to skip for pagination. Default: 0.
dataset_uriYesDataset URI, such as s3://bucket/path; API v1 only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.7.4
    • addedInput schema / properties / dataset_uri / description
      Added value: +"Dataset URI, such as s3://bucket/path; API v1 only."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records to request per page. Default:\n20."
    • addedInput schema / properties / offset / description
      Added value: +"Number of records to skip for pagination. Default: 0."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed4 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dataset_uri / title
      Removed value: -"Dataset Uri"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
  5. Addedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry behavioral context. It discloses the important v1-only limitation and points to Assets for v2, but it omits read-only confirmation, permissions, pagination behavior, and event types. This is more than nothing but not adequate for a tool with zero 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.

Conciseness4/5

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

It is a single, front-loaded sentence that communicates purpose and version constraint without filler. The '[Tool Role]' prefix is slightly mechanical but does not meaningfully hurt conciseness.

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?

The tool is simple, has a complete input schema, and has an output schema, so return values need not be explained. However, with no annotations and no sibling differentiation, the description is somewhat thin on operational context even for a simple read tool.

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%, so all three parameters are already documented in the input schema. The description adds no parameter-level semantics beyond reiterating that the dataset URI is API-v1-only, making the baseline score appropriate.

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 uses a specific verb and resource ('Gets events for a specific dataset') and adds a meaningful API-version constraint (v1 only). It does not distinguish the tool from the closely named sibling list_dataset_events or explain why both exist, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only explicit guidance is the v1-only constraint, which is useful but negative-scoped. There is no direct guidance on when to use this instead of get_dataset or list_dataset_events; the 'specific dataset' phrasing only implies scoping.

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