Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

list_variables

Retrieve and display all variables stored in Apache Airflow deployments for configuration management and workflow automation.

Instructions

List all variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
order_byNo

Implementation Reference

  • The handler function for the 'list_variables' tool. It accepts optional parameters limit, offset, and order_by, calls the Airflow VariableApi.get_variables, and returns the response as TextContent.
    async def list_variables(
        limit: Optional[int] = None,
        offset: Optional[int] = None,
        order_by: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        # Build parameters dictionary
        kwargs: Dict[str, Any] = {}
        if limit is not None:
            kwargs["limit"] = limit
        if offset is not None:
            kwargs["offset"] = offset
        if order_by is not None:
            kwargs["order_by"] = order_by
    
        response = variable_api.get_variables(**kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registration of the 'list_variables' tool (and other variable tools) via the get_all_functions which returns tuples for tool registration in the MCP server.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (list_variables, "list_variables", "List all variables", True),
            (create_variable, "create_variable", "Create a variable", False),
            (get_variable, "get_variable", "Get a variable by key", True),
            (update_variable, "update_variable", "Update a variable by key", False),
            (delete_variable, "delete_variable", "Delete a variable by key", False),
        ]
Behavior1/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. 'List all variables' reveals nothing about permissions required, rate limits, pagination behavior, return format, or whether this is a read-only operation. For a tool with 3 parameters and no output schema, this leaves critical behavioral aspects completely unspecified.

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 maximally concise at just three words with no wasted language. While severely under-specified, it's efficiently structured as a direct imperative statement without unnecessary elaboration.

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

Completeness1/5

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

Given the tool's 3 parameters, 0% schema description coverage, no annotations, and no output schema, the description 'List all variables' is completely inadequate. It fails to explain what 'variables' are in this context, how results are returned, what the parameters do, or any behavioral characteristics needed for effective tool invocation.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 3 parameters (limit, offset, order_by) have any documentation in the schema. The description 'List all variables' provides zero information about these parameters - it doesn't mention pagination, sorting, or any parameter usage at all. This fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all variables' is a tautology that essentially restates the tool name 'list_variables' without adding meaningful context. It specifies the verb 'list' and resource 'variables' but lacks any distinguishing details about scope, format, or differentiation from sibling tools like 'get_variable' or 'delete_variable'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. With sibling tools like 'get_variable' (for retrieving a single variable) and 'delete_variable' (for removal), the agent receives no indication about appropriate contexts, prerequisites, or comparative use cases for this listing operation.

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