Skip to main content
Glama

get_user

Retrieve user details from Apache Airflow clusters using the v1 API. Specify a username to access specific user information for monitoring and management.

Instructions

[Tool Role]: Gets details of a specific user (v1 API only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_user tool handler function, registered via @mcp.tool() decorator. It retrieves user details using the Airflow v1 API endpoint /users/{username}, with a check for v2 API incompatibility.
    @mcp.tool()
    async def get_user(username: str) -> Dict[str, Any]:
        """[Tool Role]: Gets details of a specific user (v1 API only)."""
        from ..functions import get_api_version
        
        api_version = get_api_version()
        if api_version == "v2":
            return {"error": "User management is not available in Airflow 3.x (API v2)", "available_in": "v1 only"}
        
        resp = await airflow_request("GET", f"/users/{username}")
        resp.raise_for_status()
        return resp.json()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'Gets details' which implies a read-only operation, but doesn't specify authentication requirements, rate limits, error conditions, or what 'details' includes. The '(v1 API only)' note provides some behavioral context about API version constraints, but overall disclosure is minimal 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just one sentence containing the core purpose and an API version note. It's front-loaded with the main function. While efficient, it may be too brief given the lack of other documentation elements.

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 document return values), no annotations, and a simple single-parameter input, the description provides minimal but adequate context for a basic read operation. However, it doesn't explain the relationship to sibling tools or provide usage guidance, leaving gaps in completeness.

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, so the description must compensate but provides no parameter information. It doesn't explain what 'username' represents, format requirements, or validation rules. The description adds no semantic meaning beyond what the bare schema provides.

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 user' which provides a clear verb ('Gets') and resource ('user'), but it doesn't distinguish this from sibling tools like 'list_users' or explain what 'details' means. The '(v1 API only)' note adds some specificity but doesn't fully differentiate the tool's purpose from alternatives.

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 like 'list_users' or other user-related operations. There's no mention of prerequisites, context, or exclusions. The '(v1 API only)' hint suggests API version constraints but doesn't explain when this matters.

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