Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_xcom_entries

Retrieve cross-communication data entries between Airflow tasks to monitor and debug workflow execution.

Instructions

Get all XCom entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
dag_run_idYes
task_idYes
map_indexNo
xcom_keyNo
limitNo
offsetNo

Implementation Reference

  • The asynchronous handler function implementing the 'get_xcom_entries' tool logic. It constructs parameters from inputs and calls the Airflow XComApi to fetch entries, returning them as formatted text content.
    async def get_xcom_entries(
        dag_id: str,
        dag_run_id: str,
        task_id: str,
        map_index: Optional[int] = None,
        xcom_key: Optional[str] = None,
        limit: Optional[int] = None,
        offset: Optional[int] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        # Build parameters dictionary
        kwargs: Dict[str, Any] = {}
        if map_index is not None:
            kwargs["map_index"] = map_index
        if xcom_key is not None:
            kwargs["xcom_key"] = xcom_key
        if limit is not None:
            kwargs["limit"] = limit
        if offset is not None:
            kwargs["offset"] = offset
    
        response = xcom_api.get_xcom_entries(dag_id=dag_id, dag_run_id=dag_run_id, task_id=task_id, **kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registration tuple for the 'get_xcom_entries' tool within the module's get_all_functions() which collects tools for central registration.
    return [
        (get_xcom_entries, "get_xcom_entries", "Get all XCom entries", True),
        (get_xcom_entry, "get_xcom_entry", "Get an XCom entry", True),
    ]
  • src/main.py:90-91 (registration)
    Central registration loop where tools from xcom module (via get_xcom_functions()) are added to the MCP app using app.add_tool().
    for func, name, description, *_ in functions:
        app.add_tool(func, name=name, description=description)
  • src/main.py:19-19 (registration)
    Import of xcom module's get_all_functions for inclusion in central tool registration.
    from src.airflow.xcom import get_all_functions as get_xcom_functions
  • Initialization of XComApi client instance used by the get_xcom_entries handler.
    xcom_api = XComApi(api_client)
Behavior1/5

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

With no annotations provided, the description carries full burden but fails to disclose behavioral traits. It doesn't indicate if this is a read-only operation, its potential impact (e.g., performance), rate limits, authentication needs, or return format. The description is too vague to inform the agent about how the tool behaves.

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 extremely concise with a single sentence, 'Get all XCom entries', which is front-loaded and wastes no words. However, this brevity comes at the cost of clarity and completeness.

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

Completeness1/5

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

Given the complexity (7 parameters, 3 required), lack of annotations, and no output schema, the description is severely incomplete. It doesn't explain what XCom entries are, how to use the tool effectively, or what to expect in return, making it inadequate for informed tool selection.

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

Parameters1/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 but adds no parameter information. It doesn't explain what parameters like 'dag_id', 'xcom_key', or 'limit' mean or how they filter results, leaving all 7 parameters undocumented beyond their titles in the schema.

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

Purpose2/5

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

The description 'Get all XCom entries' restates the tool name with minimal elaboration, making it tautological. It specifies the resource ('XCom entries') but lacks detail on what XCom entries are or how they differ from the sibling tool 'get_xcom_entry' (singular).

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

Usage Guidelines1/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 'get_xcom_entry' or other data-fetching tools. The description offers no context, prerequisites, or exclusions, leaving the agent without usage direction.

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