Skip to main content
Glama

list_variables

Retrieve all Airflow variables from an MWAA environment to manage configuration data and workflow parameters.

Instructions

List all Airflow variables in the environment.

Args: environment_name: Name of the MWAA environment limit: Number of items to return offset: Number of items to skip

Returns: Dictionary containing list of variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environment_nameYes
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the list_variables tool logic that interacts with the Airflow API.
    async def list_variables(
        self,
        environment_name: str,
        limit: Optional[int] = 100,
        offset: Optional[int] = 0,
    ) -> Dict[str, Any]:
        """List variables via Airflow API."""
        params: Dict[str, Any] = {"limit": limit, "offset": offset}
        return self._invoke_airflow_api(
            environment_name, "GET", "/variables", params=params
        )
  • The MCP tool registration and entry point wrapper for list_variables.
    @mcp.tool(name="list_variables")
    async def list_variables(
        environment_name: str,
        limit: Optional[int] = 100,
        offset: Optional[int] = 0,
    ) -> Dict[str, Any]:
        """List all Airflow variables in the environment.
    
        Args:
            environment_name: Name of the MWAA environment
            limit: Number of items to return
            offset: Number of items to skip
    
        Returns:
            Dictionary containing list of variables
        """
        limit_int = int(limit) if limit is not None else 100
        offset_int = int(offset) if offset is not None else 0
    
        return await tools.list_variables(environment_name, limit_int, offset_int)
Behavior2/5

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

No annotations provided, yet description provides minimal behavioral context beyond the Returns clause stating response format. Omits authentication requirements, rate limits, and what constitutes a valid environment_name.

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?

Uses structured Google-style docstring format (Args/Returns) that front-loads the purpose statement. Appropriate length given the need to document parameters that the schema leaves undocumented.

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?

Adequate for a listing tool with existing output schema, but gaps remain in behavioral disclosure (error handling, pagination behavior) thatannotations would typically cover.

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?

Excellent compensation for 0% schema coverage: Args section documents all 3 parameters (environment_name, limit, offset) with clear semantics including MWAA context for the environment parameter.

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?

Clearly states 'List all Airflow variables' with specific verb and resource. Distinguishes from siblings (list_dags, list_connections) by specifying 'Airflow variables,' though MWAA context is buried in parameter descriptions rather than the main statement.

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 explicit guidance on when to use this tool versus siblings, no pagination best practices for limit/offset parameters, and no mention of error conditions (e.g., invalid environment_name).

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/paschmaria/mwaa-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server