Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_variable

Retrieve the value of a specific Apache Airflow variable by its exact key to resolve configuration values during monitoring or automation tasks.

Instructions

[Tool Role]: Gets the value of a specific variable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "variable_key": "<variable_key>"
    },
    "name": "get_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
variable_keyYesExact key of the Airflow variable.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / variable_key / description
      Added value: +"Exact key of the Airflow variable."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / variable_key / title
      Removed value: -"Variable Key"
  5. First observed

TDQS

B3.1/5.0
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 behavioral burden. 'Gets' implies a read operation, but the description does not state what happens if the variable is missing, whether variables may contain sensitive values, or any permission requirements.

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?

The description is a single front-loaded sentence with no wasted elaboration. The '[Tool Role]:' prefix is minor metadata overhead but does not materially hurt readability.

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

Completeness4/5

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

This is a simple one-parameter getter with full schema description coverage and an output schema, so the description is mostly complete for calling the tool. The main missing context is error behavior for nonexistent variables and any sensitivity handling, which are not covered elsewhere.

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 coverage is 100%, and the schema already documents variable_key as the exact key of the Airflow variable. The description adds no additional parameter semantics beyond saying it retrieves a specific variable, so the baseline of 3 is appropriate.

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 gives a clear verb and resource: it gets the value of a specific variable. It does not explicitly contrast with the sibling list_variables, so an agent can infer but not be certain why to choose one over the other.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as list_variables. The purpose implies it is used to retrieve a known variable, but the description does not guide the agent on when this is preferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.