Skip to main content
Glama
astronomer

astro-airflow-mcp

Official
by astronomer

get_variable

Retrieve an Airflow variable by key to access its value and metadata, enabling DAG configuration and sharing settings across workflows.

Instructions

Get a specific Airflow variable by key.

Use this tool when the user asks about:

  • "What's the value of variable X?" or "Show me variable Y"

  • "Get variable Z" or "What does variable A contain?"

  • "What's stored in variable B?" or "Look up variable C"

Variables are key-value pairs stored in Airflow's metadata database that can be accessed by DAGs at runtime. They're commonly used for configuration values, API keys, or other settings that need to be shared across DAGs.

Returns variable information including:

  • key: The variable's key/name

  • value: The variable's value (may be masked if marked as sensitive)

  • description: Optional description of the variable's purpose

Args: variable_key: The key/name of the variable to retrieve

Returns: JSON with the variable's key, value, and metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variable_keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes return values including potential masking of sensitive values, and explains that it's a read operation. Lacks mention of any side effects, but none expected.

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?

Well-structured with headings and bullet points, but some explanatory text about variables could be shortened without losing value.

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

Completeness5/5

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

For a simple getter with one parameter and no annotations, the description is complete, covering purpose, usage, and return format.

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

Parameters5/5

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

The single parameter 'variable_key' is fully described with its purpose and role, compensating for the 0% schema coverage.

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

Purpose5/5

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

The description clearly states 'Get a specific Airflow variable by key' and provides specific example user queries, distinguishing it from list_variables.

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

Usage Guidelines4/5

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

Provides explicit usage examples and context about when to use, but does not explicitly mention when not to use or alternatives beyond the given examples.

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/astronomer/astro-airflow-mcp'

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