Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_xcom_entry

Retrieve a specific XCom entry by DAG ID, run ID, task ID, and XCom key to inspect inter-task data passed during an Airflow workflow run.

Instructions

[Tool Role]: Gets a specific XCom entry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dag_id": "<dag_id>",
      "dag_run_id": "<dag_run_id>",
      "task_id": "<task_id>",
      "xcom_key": "<xcom_key>"
    },
    "name": "get_xcom_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
dag_idYesExact DAG identifier, as returned by list_dags; not its display name.
task_idYesExact task identifier within the selected DAG.
xcom_keyYesExact XCom key for the selected task instance.
dag_run_idYesExact DAG run identifier for the selected DAG.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.7.4
    • addedInput schema / properties / dag_id / description
      Added value: +"Exact DAG identifier, as returned by list_dags; not its\ndisplay name."
    • addedInput schema / properties / dag_run_id / description
      Added value: +"Exact DAG run identifier for the selected DAG."
    • addedInput schema / properties / task_id / description
      Added value: +"Exact task identifier within the selected DAG."
    • addedInput schema / properties / xcom_key / description
      Added value: +"Exact XCom key for the selected task instance."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed5 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dag_id / title
      Removed value: -"Dag Id"
    • removedInput schema / properties / dag_run_id / title
      Removed value: -"Dag Run Id"
    • removedInput schema / properties / task_id / title
      Removed value: -"Task Id"
    • removedInput schema / properties / xcom_key / title
      Removed value: -"Xcom Key"
  5. Changed1 schema field changedv1.0.0
    • removedInput schema / properties / map_index
      Removed value: -{
      -  "default": -1,
      -  "title": "Map Index",
      -  "type": "integer"
      -}
  6. First observed

TDQS

C2.9/5.0
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 behavioral burden, yet it says nothing about read-only nature, behavior when the key does not exist (error vs empty), or permission requirements. The presence of an output schema removes the need to explain return values, but the disclosure gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste, but it is under-specified rather than tight—brevity comes at the cost of any operational context.

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

Completeness3/5

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

With a full output schema and 100% parameter description coverage, the structured data supplies most of what an agent needs to invoke the tool correctly. The missing piece is behavioral context, which no annotation covers.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with each of the four identifiers documented in the schema itself. The description adds no additional semantics, so the baseline 3 applies.

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 states a specific verb and resource ("Gets a specific XCom entry"), which is clearly distinct from list_xcom_entries by the singular/plural naming. It does not explicitly call out the sibling relationship or scope, but an agent can infer the get-vs-list distinction.

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?

There is no guidance on when to use this tool versus list_xcom_entries, nor any prerequisites such as needing a completed task instance or existing key. The agent must infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.