Skip to main content
Glama
Sign In
MCP-Airflow-API

MCP-Airflow-API

by call518
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_config_options

Find Airflow configuration options by matching a term against option names or values, so you can identify relevant settings without scanning the full configuration.

Instructions

[Tool Role]: Searches for configuration options matching a term.

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": {
      "search_term": "<search_term>"
    },
    "name": "search_config_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_termYesCase-insensitive substring to find in option names or values.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / search_term / description
      Added value: +"Case-insensitive substring to find in option names\nor values."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / search_term / title
      Removed value: -"Search Term"
  5. Addedv1.0.0

TDQS

C2.9/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 disclosure burden, and it says nothing about read-only nature, whether results span all config sections, result limits, ordering, or matching scope. The only behavioral detail (case-insensitive substring on names or values) lives in the schema, not the description.

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?

One front-loaded sentence with no redundancy, but the '[Tool Role]:' prefix is structural noise and the brevity comes partly from under-specification rather than efficiency.

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?

An output schema exists, so return values need not be explained, and the tool is a simple one-parameter search. Still, with zero annotations the description leaves read-only status and search scope undisclosed, which is the minimum viable rather than fully complete.

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 100% and the single parameter is well documented as a case-insensitive substring over names or values. The phrase 'matching a term' adds nothing beyond that, so baseline 3 applies.

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?

States a specific verb (Searches) and resource (configuration options) with the matching criterion. The 'search' verb does implicitly distinguish it from siblings like get_config and list_config_sections, though the description never names those siblings.

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 statement of when to use this versus get_config, get_config_section, or list_config_sections. An agent must infer that 'search' means 'use when you don't know the exact option name', which is reasonable but entirely unstated.

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

Deploy Server

Other Tools