Skip to main content
Glama
astronomer

astro-airflow-mcp

Official
by astronomer

list_import_errors

Identify and troubleshoot DAG files that failed to parse or load in Apache Airflow. Returns import error details including stack traces, file paths, and timestamps to help diagnose missing imports, syntax errors, and module issues.

Instructions

Get import errors from DAG files that failed to parse or load.

Use this tool when the user asks about:

  • "Are there any import errors?" or "Show me import errors"

  • "Why isn't my DAG showing up?" or "DAG not appearing in Airflow"

  • "What DAG files have errors?" or "Show me broken DAGs"

  • "Check for syntax errors" or "Are there any parsing errors?"

  • "Why is my DAG file failing to load?"

Import errors occur when DAG files have problems that prevent Airflow from parsing them, such as:

  • Python syntax errors

  • Missing imports or dependencies

  • Module not found errors

  • Invalid DAG definitions

  • Runtime errors during file parsing

Returns import error details including:

  • import_error_id: Unique identifier for the error

  • timestamp: When the error was detected

  • filename: Path to the DAG file with the error

  • stack_trace: Complete error message and traceback

Returns: JSON with list of import errors and their stack traces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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. It discloses the return fields (import_error_id, timestamp, filename, stack_trace) and explains the causes of import errors. It implies a read-only operation but does not discuss potential limitations like pagination or performance. Still, it is adequately transparent.

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?

The description is longer than necessary, with repeated information (e.g., causes of import errors are listed twice). The first sentence is clear, but the bulleted examples could be condensed. Some sentences do not add new value.

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

Completeness4/5

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

Given the low complexity (no parameters, output schema present), the description is fairly complete. It covers purpose, typical use cases, causes, and return fields. It does not mention behavior for empty results or error cases, but that is minor.

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

Parameters4/5

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

The input schema has zero parameters, so coverage is vacuously 100%. The description adds value by explaining the output fields beyond the schema, which is the only semantic context needed. Baseline is 3, but the extra output detail justifies a 4.

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

Purpose5/5

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

The description clearly states the purpose: 'Get import errors from DAG files that failed to parse or load.' It uses a specific verb-resource pair and distinguishes from sibling tools (none of which list import errors). The examples reinforce the specific resource.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a list of explicit user queries that map to this tool, providing clear usage context. However, it does not mention when not to use it or provide alternative sibling tools for related issues (e.g., diagnose_dag_run for run failures).

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/astronomer/astro-airflow-mcp'

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