Skip to main content
Glama

get_provider

Retrieve details of a specific provider package in Apache Airflow to inspect its configuration and capabilities for cluster management.

Instructions

[Tool Role]: Gets details of a specific provider package.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for the 'get_provider' tool, decorated with @mcp.tool() for registration. It fetches provider details from the Airflow API endpoint /providers/{provider_name}.
    async def get_provider(provider_name: str) -> Dict[str, Any]:
        """[Tool Role]: Gets details of a specific provider package."""
        resp = await airflow_request("GET", f"/providers/{provider_name}")
        resp.raise_for_status()
        return resp.json()
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. It only states the action ('Gets details') without mentioning permissions, rate limits, error handling, or output format. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 a single sentence, front-loaded with the tool's role. There is no wasted text, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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?

Given the tool has an output schema (which should cover return values) and only one parameter, the description is minimally adequate. However, with no annotations and low schema coverage, it lacks context on usage, behavioral traits, and parameter details, making it incomplete for effective agent use without additional structured data.

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?

The description does not add any meaning beyond the input schema, which has 0% description coverage. It mentions a 'specific provider package' but doesn't explain what 'provider_name' represents or its format. With one parameter and low schema coverage, the description fails to compensate, resulting in minimal added value over the schema.

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 states the tool 'Gets details of a specific provider package,' which provides a basic verb (gets) and resource (provider package). However, it doesn't differentiate from siblings like 'list_providers' or 'get_config,' leaving the purpose somewhat vague. The description is functional but lacks specificity about what 'details' entail.

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. With siblings like 'list_providers' (likely for listing multiple providers) and 'get_config' (for configuration details), the description fails to indicate that this tool is for retrieving detailed information about a single, specific provider package, leaving usage context implied at best.

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/call518/MCP-Airflow-API'

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