Skip to main content
Glama

get_import_error

Retrieve specific import errors from Apache Airflow clusters to diagnose and resolve DAG import failures during workflow execution.

Instructions

[Tool Role]: Retrieves a specific import error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
import_error_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the get_import_error tool. It fetches the specific import error details from the Airflow REST API using the provided import_error_id.
    @mcp.tool()
    async def get_import_error(import_error_id: int) -> Dict[str, Any]:
        """[Tool Role]: Retrieves a specific import error."""
        resp = await airflow_request("GET", f"/importErrors/{import_error_id}")
        resp.raise_for_status()
        return resp.json()
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. It states the tool 'retrieves' data, implying a read-only operation, but doesn't clarify authentication needs, rate limits, error handling, or what 'retrieves' entails (e.g., returns full error details). For a tool with no annotation coverage, this leaves significant behavioral gaps.

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—a single sentence that directly states the tool's role. It's front-loaded with no wasted words, making it easy to parse quickly. Every part of the sentence earns its place by conveying the core action.

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?

Given the tool has an output schema (which handles return values), 1 parameter with low complexity, and no annotations, the description is minimally complete. It covers the basic purpose but lacks context on usage, behavioral traits, or parameter details, leaving gaps that could hinder effective tool selection and invocation.

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 description adds minimal meaning beyond the input schema, which has 0% description coverage. It implies the parameter 'import_error_id' identifies a specific error to retrieve, but doesn't explain format, constraints, or sourcing. With only 1 parameter and no schema descriptions, the baseline is high, but the description doesn't fully compensate for the lack of schema details.

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 'retrieves a specific import error', which provides a clear verb ('retrieves') and resource ('import error'). However, it doesn't distinguish this tool from sibling tools like 'list_import_errors' or 'all_dag_import_summary', leaving the scope of 'specific' somewhat vague. The purpose is understandable but lacks sibling differentiation.

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 prerequisites (e.g., needing an import error ID), exclusions, or comparisons to sibling tools like 'list_import_errors' for bulk retrieval. Usage is implied by the parameter name but not explicitly stated.

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/call518/MCP-Airflow-API'

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