Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_value

Retrieve specific configuration options from Apache Airflow deployments using Bearer token authentication for secure API access.

Instructions

Get a specific option from configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYes
optionYes

Implementation Reference

  • The async handler function that implements the core logic of the 'get_value' tool. It retrieves a specific configuration option using the Airflow config API and formats the response as MCP TextContent.
    async def get_value(
        section: str, option: str
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = config_api.get_value(section=section, option=option)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The get_all_functions() defines and returns the tuple for registering the 'get_value' tool, including its name, description, and read-only flag. This list is later used by main.py to add the tool to 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 [
            (get_config, "get_config", "Get current configuration", True),
            (get_value, "get_value", "Get a specific option from configuration", True),
        ]
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 of behavioral disclosure. While 'Get' implies a read-only operation, the description doesn't specify whether this requires authentication, what happens if the option doesn't exist, whether there are rate limits, or what format the returned value takes. This leaves significant behavioral gaps for a tool with no 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 extremely concise with just one sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it easy to parse quickly.

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?

For a tool with 2 required parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'configuration' refers to in this system, what values might be returned, error conditions, or how this differs from similar tools. The context demands more comprehensive documentation.

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

Parameters2/5

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

The input schema has 0% description coverage, providing only parameter names ('section', 'option') without explaining what they mean. The description adds minimal value by implying these parameters identify a 'specific option from configuration', but doesn't clarify what sections or options are available, their format, or examples. This is insufficient compensation for the schema's lack of documentation.

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

Purpose3/5

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

The description 'Get a specific option from configuration' clearly states the verb ('Get') and resource ('option from configuration'), but it's somewhat vague about what 'configuration' refers to in this context. It doesn't distinguish this tool from similar siblings like 'get_config' or 'get_variable', which also retrieve configuration-like data.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'get_config', 'get_variable', 'get_connection', etc., there's no indication of what makes this tool unique or when it should be preferred over other configuration-retrieval tools.

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