Skip to main content
Glama
deenesjakoruzh
yangkyeongmo

MCP Server for Apache Airflow

by yangkyeongmo
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_dag_dataset_queued_event

Remove a queued dataset event from a DAG to manage event-driven workflows and prevent unnecessary DAG triggers in Apache Airflow.

Instructions

Delete a queued Dataset event for a DAG

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
uriYes

Implementation Reference

  • src/airflow/dataset.py:135-140 (handler)
    The handler function implementing the 'delete_dag_dataset_queued_event' tool logic by calling the Airflow DatasetApi to delete the queued event for the specified DAG and URI.
    async def delete_dag_dataset_queued_event(
    dag_id: str,
    uri: str,
) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
    response = dataset_api.delete_dag_dataset_queued_event(dag_id=dag_id, uri=uri)
    return [types.TextContent(type="text", text=str(response.to_dict()))]
  • src/airflow/dataset.py:20-25 (registration)
    The registration entry for the 'delete_dag_dataset_queued_event' tool in the get_all_functions list, which is used to register MCP tools.
    (
    delete_dag_dataset_queued_event,
    "delete_dag_dataset_queued_event",
    "Delete a queued Dataset event for a DAG",
    False,
),

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is 'Delete', implying a destructive mutation, but does not clarify permissions needed, whether the deletion is reversible, or what happens on success/failure. This is a significant gap for a mutation tool.

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 no wasted words. It is front-loaded with the core action and resource, 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?

For a destructive mutation tool with no annotations, 0% schema coverage, and no output schema, the description is inadequate. It lacks details on behavior, parameters, outcomes, and error handling, leaving critical gaps for an agent to use it correctly.

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%, so the description must compensate by explaining parameters. It mentions 'a queued Dataset event for a DAG', which hints at 'dag_id' and 'uri' but does not define their semantics, formats, or examples. The description adds minimal value beyond the schema's structure.

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 action ('Delete') and the target resource ('a queued Dataset event for a DAG'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'delete_dag_dataset_queued_events' (plural) or 'delete_dataset_queued_events', leaving some ambiguity about scope.

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 does not mention prerequisites, such as needing an existing queued event, or specify scenarios where this deletion is appropriate, leaving the agent to infer usage from the 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/yangkyeongmo/mcp-server-apache-airflow'

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