Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_user

Retrieve details for a specific Apache Airflow user by exact username through API v1 to inspect account information without direct API calls.

Instructions

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

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": {
      "username": "<username>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesExact Airflow username (API v1 only).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / username / description
      Added value: +"Exact Airflow username (API v1 only)."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / username / title
      Removed value: -"Username"
  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 burden, yet it says nothing about required permissions, behavior for unknown usernames, or whether roles/attributes are returned. 'Gets' implies a read, but that is the only behavioral signal in the text.

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 short sentence with the resource and scope stated immediately. The '[Tool Role]:' prefix adds no information but costs little.

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 and the parameter is fully documented, so the remaining gaps are modest. Still, for a lookup tool with no annotations, the description should at least say what happens when the user does not exist and how it relates to list_users.

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 the single 'username' parameter including the exact-match and v1-only constraint. The description repeats rather than extends that information, so the 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 and resource ('Gets details of a specific user') and adds a scope qualifier ('v1 API only'). It does not explicitly contrast with the sibling list_users, so it stops short of a 5.

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 guidance on when to use this versus list_users (to enumerate users) or why the v1-only restriction matters. The only hint is the parenthetical API version note, which implies a constraint rather than a selection rule.

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