Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

delete_dag_dataset_queued_events

Remove queued Dataset events for a specific DAG to manage event backlog and maintain workflow efficiency in Airflow deployments.

Instructions

Delete queued Dataset events for a DAG

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
beforeNo

Implementation Reference

  • The main handler function for the 'delete_dag_dataset_queued_events' tool, which calls the underlying dataset_api to delete queued dataset events for a given DAG.
    async def delete_dag_dataset_queued_events(
        dag_id: str,
        before: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        kwargs: Dict[str, Any] = {}
        if before is not None:
            kwargs["before"] = before
    
        response = dataset_api.delete_dag_dataset_queued_events(dag_id=dag_id, **kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registration of the tool in the get_all_functions() list, including the function reference, name, description, and mutability flag.
    (
        delete_dag_dataset_queued_events,
        "delete_dag_dataset_queued_events",
        "Delete queued Dataset events for a DAG",
        False,
    ),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete', implying a destructive mutation, but doesn't disclose critical behaviors: whether deletion is permanent, requires specific permissions, affects DAG execution, or has side effects. For a destructive tool with zero annotation coverage, this is a significant gap in behavioral context.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it easy to parse quickly. Every word earns its place in conveying the essential purpose.

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 a destructive tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks parameter details, behavioral warnings, usage context, and output expectations. For this complexity level, it should provide more guidance on what 'delete' entails and how to use the parameters.

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 schema provides no parameter documentation. The description mentions 'for a DAG', which hints at the 'dag_id' parameter, but doesn't explain 'before' or provide any details on parameter formats, constraints, or examples. It adds minimal value beyond what's inferable from the tool name.

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 'Delete queued Dataset events for a DAG' clearly states the action (delete) and target (queued Dataset events for a DAG). It distinguishes from siblings like 'delete_dag_dataset_queued_event' (singular) and 'delete_dataset_queued_events' (not DAG-specific), but doesn't explicitly contrast them. The purpose is specific but lacks full sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'delete_dag_dataset_queued_event' (singular) or 'clear_dag_run'. The description implies it's for deleting queued events, but offers no context on prerequisites, timing, or exclusions. Usage is implied from the name and purpose 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/nikhil-ganage/mcp-server-airflow-token'

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