Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_xcom_entry

Retrieve cross-communication data between Airflow tasks by specifying DAG, run, task, and XCom key parameters.

Instructions

Get an XCom entry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
dag_run_idYes
task_idYes
xcom_keyYes
map_indexNo
deserializeNo
stringifyNo

Implementation Reference

  • The async handler function that implements the logic for the 'get_xcom_entry' tool by calling the Airflow XCom API and formatting the response as MCP TextContent.
    async def get_xcom_entry(
        dag_id: str,
        dag_run_id: str,
        task_id: str,
        xcom_key: str,
        map_index: Optional[int] = None,
        deserialize: Optional[bool] = None,
        stringify: Optional[bool] = 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 deserialize is not None:
            kwargs["deserialize"] = deserialize
        if stringify is not None:
            kwargs["stringify"] = stringify
    
        response = xcom_api.get_xcom_entry(
            dag_id=dag_id, dag_run_id=dag_run_id, task_id=task_id, xcom_key=xcom_key, **kwargs
        )
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The registration function that provides the tuple for the 'get_xcom_entry' tool, including its name, description, and read-only flag, which is imported and used in main.py to register the tool via app.add_tool.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_xcom_entries, "get_xcom_entries", "Get all XCom entries", True),
            (get_xcom_entry, "get_xcom_entry", "Get an XCom entry", True),
        ]
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions are required, whether it's idempotent, what happens on failure, or what the return format looks like. 'Get' implies retrieval but lacks any behavioral context about rate limits, side effects, or error conditions.

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 maximally concise with a single four-word phrase. While severely under-specified, it contains no wasted words and is appropriately sized for its limited content. The structure is front-loaded with the core action, though it lacks supporting details.

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?

For a tool with 7 parameters, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what XCom entries are, how they're used in the system, what values are returned, or any behavioral characteristics. The agent would struggle to use this tool correctly without extensive external knowledge.

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?

With 0% schema description coverage and 7 parameters (4 required), the description provides zero information about parameter meanings or usage. It doesn't explain what 'dag_id', 'xcom_key', 'deserialize', or any other parameters represent, nor their relationships. The description fails to compensate for the complete lack of schema documentation.

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 an XCom entry' is a tautology that restates the tool name with minimal elaboration. It specifies the verb 'Get' and resource 'XCom entry', but doesn't explain what an XCom entry is or how it differs from sibling tools like 'get_xcom_entries' (plural). The purpose is vague without context about what XCom represents in this system.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this tool is appropriate versus 'get_xcom_entries', or any contextual constraints. The agent must infer usage solely from the tool name and parameters.

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