Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_plugins

Retrieve all installed plugins in Apache Airflow to inspect available extensions and integrations for workflow management.

Instructions

[Tool Role]: Lists all installed plugins in the Airflow system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_airflow_api/tools/common_tools.py:941-947 (handler)
    The core handler function for the 'list_plugins' tool. It makes an HTTP GET request to the Airflow '/plugins' API endpoint and returns the JSON response containing all installed plugins.
    @mcp.tool()
async def list_plugins() -> Dict[str, Any]:
    """[Tool Role]: Lists all installed plugins in the Airflow system."""
    resp = await airflow_request("GET", "/plugins")
    resp.raise_for_status()
    return resp.json()
  • src/mcp_airflow_api/tools/v1_tools.py:23-23 (registration)
    Registration of common tools (including list_plugins) for Airflow API v1 by calling register_common_tools.
    common_tools.register_common_tools(mcp)
  • src/mcp_airflow_api/tools/v2_tools.py:24-24 (registration)
    Registration of common tools (including list_plugins) for Airflow API v2 by calling register_common_tools.
    common_tools.register_common_tools(mcp)
  • src/mcp_airflow_api/mcp_main.py:385-385 (registration)
    Top-level registration call for v1 tools in the main MCP server initialization.
    v1_tools.register_tools(mcp)
  • src/mcp_airflow_api/mcp_main.py:389-389 (registration)
    Top-level registration call for v2 tools in the main MCP server initialization.
    v2_tools.register_tools(mcp)

Tool Definition Quality

B3.2/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 full burden. It states the action ('Lists all installed plugins') but does not disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the output format entails. This is a significant gap for a tool with zero annotation coverage.

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 that directly states the tool's role without any wasted words. It is front-loaded and appropriately sized for a simple listing tool, earning its place clearly.

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's simplicity (0 parameters, no annotations, but has an output schema), the description is minimally adequate. It states what the tool does but lacks behavioral context and usage guidelines. The output schema may cover return values, but the description should still address when and how to use it, leaving some gaps.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description does not add parameter details, which is unnecessary here, and baseline is 4 for zero parameters as it avoids redundancy.

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 verb ('Lists') and resource ('all installed plugins in the Airflow system'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'list_providers' or 'list_connections', which are similar listing operations but for different resources, so it misses full 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 lacks context such as prerequisites, when it's appropriate (e.g., for auditing or debugging), or comparisons to other listing tools like 'list_providers' for similar functions, leaving the agent without usage direction.

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