Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_import_error

Retrieve specific import error details from Apache Airflow deployments by providing the error ID to diagnose and resolve data pipeline issues.

Instructions

Get a specific import error by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
import_error_idYes

Implementation Reference

  • The async handler function that implements the core logic of the 'get_import_error' tool. It takes an import_error_id, calls the Airflow ImportErrorApi to retrieve the specific import error, and returns it formatted as MCP TextContent.
    async def get_import_error(
        import_error_id: int,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = import_error_api.get_import_error(import_error_id=import_error_id)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The module-level get_all_functions that returns the registration tuple for 'get_import_error', linking the handler function to its name and description for inclusion in the central MCP tool registry.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_import_errors, "get_import_errors", "List import errors", True),
            (get_import_error, "get_import_error", "Get a specific import error by ID", True),
        ]
  • Initialization of the ImportErrorApi client instance used by the get_import_error handler.
    import_error_api = ImportErrorApi(api_client)
  • src/main.py:90-92 (registration)
    The generic registration loop in main.py where all tools, including get_import_error, are added to the MCP app via app.add_tool using data from module get_all_functions.
    for func, name, description, *_ in functions:
        app.add_tool(func, name=name, description=description)
  • src/main.py:12-12 (registration)
    Import of the get_all_functions from importerror.py into the central main.py registry.
    from src.airflow.importerror import get_all_functions as get_importerror_functions
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits such as read/write nature, error responses, authentication needs, or rate limits, leaving significant gaps for a tool that likely queries data.

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 a single, efficient sentence with no wasted words, making it easy to parse. It's appropriately sized for a simple tool and front-loaded with the core action.

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

Completeness2/5

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

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, return values, and error handling, making it inadequate for a tool that likely involves data retrieval.

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

Parameters2/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 details beyond the name 'import_error_id'. It doesn't explain what an import error ID is, its format, or where to find it, failing to address the coverage gap.

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 clearly states the action ('Get') and target resource ('a specific import error by ID'), making the purpose unambiguous. However, it doesn't differentiate from its sibling 'get_import_errors' (plural), which likely retrieves multiple errors, so it misses full sibling 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?

No guidance is provided on when to use this tool versus alternatives like 'get_import_errors'. The description implies usage for a single error by ID but doesn't specify prerequisites, error handling, or contextual recommendations.

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