Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

delete_variable

Remove a specific variable from Apache Airflow by providing its key, enabling cleanup of configuration data in Airflow deployments.

Instructions

Delete a variable by key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Implementation Reference

  • The async handler function that implements the 'delete_variable' tool. It calls the Airflow VariableApi to delete the variable by key and returns a textual representation of the response.
    async def delete_variable(key: str) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = variable_api.delete_variable(variable_key=key)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Defines the list of tools for the variable module, including the tuple for 'delete_variable' used for registration.
    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),
        ]
  • src/main.py:90-92 (registration)
    The loop in main() that registers all tools from imported modules (including variable tools) by calling app.add_tool.
    for func, name, description, *_ in functions:
        app.add_tool(func, name=name, description=description)
  • The VariableApi instance used by all variable tools, including delete_variable.
    variable_api = VariableApi(api_client)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool deletes a variable, implying a destructive mutation, but lacks details on permissions required, whether deletion is permanent or reversible, error handling (e.g., if the key doesn't exist), or side effects. This is a significant gap for a destructive operation 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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse at a glance.

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 the tool's destructive nature, lack of annotations, no output schema, and low parameter coverage, the description is inadequate. It doesn't address behavioral aspects like safety, errors, or return values, leaving the agent with insufficient context to use the tool reliably in complex scenarios.

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 0%, so the description must compensate. It mentions 'by key', which clarifies the single parameter's role, but doesn't explain what a 'key' is (e.g., format, constraints, or examples). This adds minimal value beyond the schema's property name 'key', leaving the parameter largely undocumented.

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 action ('Delete') and resource ('a variable by key'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'delete_connection' or 'delete_dag', but the specific resource 'variable' is unambiguous within the context of the toolset.

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., the variable must exist), contrast with 'clear_variable' if such a tool existed, or specify error conditions. The description is purely functional without contextual advice.

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