Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_plugins

Retrieve a list of loaded plugins from Apache Airflow deployments to monitor and manage available extensions.

Instructions

Get a list of loaded plugins

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • The main handler function implementing the 'get_plugins' MCP tool. It accepts optional limit and offset parameters, calls the underlying Airflow PluginApi.get_plugins, and returns the response as a TextContent list.
    async def get_plugins(
        limit: Optional[int] = None,
        offset: Optional[int] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        """
        Get a list of loaded plugins.
    
        Args:
            limit: The numbers of items to return.
            offset: The number of items to skip before starting to collect the result set.
    
        Returns:
            A list of loaded plugins.
        """
        # Build parameters dictionary
        kwargs: Dict[str, Any] = {}
        if limit is not None:
            kwargs["limit"] = limit
        if offset is not None:
            kwargs["offset"] = offset
    
        response = plugin_api.get_plugins(**kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Local registration of the 'get_plugins' tool via the get_all_functions list, which is imported and used in src/main.py to register all tools.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (get_plugins, "get_plugins", "Get a list of loaded plugins", True),
        ]
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 for behavioral disclosure. 'Get a list' implies a read operation, but the description doesn't specify whether this requires authentication, what format the list returns, whether it's paginated, or any rate limits. For a tool with zero 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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple list-retrieval tool. Every word earns its place.

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 2 undocumented parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what a 'loaded plugin' means in this context, how results are structured, or how parameters affect the operation. For a tool with this level of complexity and poor structured data coverage, the description should provide more context.

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 parameters 'limit' and 'offset' are completely undocumented in the schema. The description provides no information about these parameters, their purpose, or how they affect the returned list. The description fails to compensate for the schema's lack of documentation.

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 'Get' and resource 'list of loaded plugins', making the purpose unambiguous. It doesn't differentiate from sibling tools, but since no other plugin-related tools exist in the sibling list, this is adequate. The description avoids tautology by specifying what kind of list is retrieved.

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. There are no explicit instructions about context, prerequisites, or comparisons with other tools in the sibling list. The agent must infer usage based solely on the tool name and description.

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