Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_dag_dataset_queued_event

Retrieve queued Dataset events for Airflow DAGs to monitor data pipeline triggers and dependencies.

Instructions

Get a queued Dataset event for a DAG

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
uriYes

Implementation Reference

  • The main handler function that executes the tool logic: calls the Airflow dataset_api to retrieve the queued Dataset event for a given DAG ID and URI, then formats the response as MCP TextContent.
    async def get_dag_dataset_queued_event(
        dag_id: str,
        uri: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = dataset_api.get_dag_dataset_queued_event(dag_id=dag_id, uri=uri)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registers the tool in the get_all_functions() list with its name, description, and read-only flag.
    (get_dag_dataset_queued_event, "get_dag_dataset_queued_event", "Get a queued Dataset event for a DAG", True),
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. The description only states what the tool does ('Get a queued Dataset event'), but doesn't disclose any behavioral traits such as whether this is a read-only operation, what format the event data is returned in, error conditions, or performance characteristics. For a tool with zero annotation coverage, this is inadequate.

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?

The description is extremely concise at just 7 words, which is appropriate for a simple-sounding retrieval tool. It's front-loaded with the core purpose. However, the extreme brevity comes at the cost of completeness, making it more under-specified than optimally concise.

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 that there are no annotations, no output schema, and the input schema has 0% description coverage, the description is incomplete. It doesn't explain what a 'queued Dataset event' is, what data is returned, or how the two parameters identify the specific event. For a tool that appears to retrieve potentially complex event data, this minimal description leaves too many questions unanswered.

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?

The input schema has 0% description coverage, so the schema provides no semantic information about the two required parameters (dag_id and uri). The description doesn't mention either parameter or explain what they represent, leaving the agent to guess their meaning and format. The description fails to compensate for the schema's lack of parameter documentation.

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

Purpose3/5

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

The description states the tool's purpose as 'Get a queued Dataset event for a DAG', which is a clear verb+resource combination. However, it doesn't distinguish this tool from its sibling 'get_dag_dataset_queued_events' (plural), which appears to fetch multiple events. The description is vague about whether this retrieves a single specific event or just any queued event.

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 when to use this versus 'get_dag_dataset_queued_events' (plural) or 'get_dataset_queued_events', nor does it specify prerequisites or exclusions. 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/nikhil-ganage/mcp-server-airflow-token'

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