Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_import_error

Retrieves a specific DAG import error by its numeric ID, helping you inspect and troubleshoot failed Airflow DAG imports.

Instructions

[Tool Role]: Retrieves a specific import error.

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": {
      "import_error_id": "<import_error_id>"
    },
    "name": "get_import_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
import_error_idYesNumeric identifier of the DAG import error.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / import_error_id / description
      Added value: +"Numeric identifier of the DAG import error."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / import_error_id / title
      Removed value: -"Import Error Id"
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears full disclosure burden. 'Retrieves' implies a safe read, and an output schema exists to cover the return shape, but the description says nothing about behavior when the ID does not exist or any permission requirements. For a simple read tool this is acceptable but thin.

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

Conciseness4/5

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

One short front-loaded sentence with no waste. The '[Tool Role]:' prefix is mild boilerplate, and the extreme brevity edges toward under-specification rather than optimal conciseness.

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 one fully documented parameter and an output schema covering return values, the description is nearly sufficient for calling the tool. However it omits sibling differentiation from list_import_errors and any not-found behavior, leaving clear gaps.

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 a single required parameter already documented as a numeric identifier of a DAG import error. The description adds no meaning beyond the schema, 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?

States a specific verb (retrieves) and resource (a specific import error), and the word 'specific' implicitly contrasts with listing siblings. It stops short of naming list_import_errors or explaining what an import error record contains, but the core purpose is unambiguous.

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 explicit when-to-use guidance, no prerequisites, and no mention of the alternative sibling list_import_errors for browsing errors. The agent must infer from 'specific' that this requires a known ID.

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