MCP-Airflow-API

list_roles

List all user roles defined in the Airflow system via the v1 API, with optional pagination controls for efficient browsing.

Instructions

[Tool Role]: Lists all roles in the Airflow system (v1 API only).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_roles"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the 'v1 API only' constraint and implies a read-only list operation, which is useful. However, it omits any details about pagination behavior or potential side effects, though for a list operation this is a minor gap.

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 a single concise sentence that front-loads the tool's purpose and scope. Every word earns its place, with no redundant information.

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?

For a simple list tool with an output schema, the description is minimally complete. However, it leaves the pagination behavior implicit, and the 'all roles' wording in conflict with the limit/offset parameters creates ambiguity. It could benefit from clarifying that the list is paginated.

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 description does not explain the limit and offset parameters or how pagination works. The phrase 'Lists all roles' could mislead an agent into expecting no pagination, even though the schema has a default limit of 20. The description adds no value beyond the schema.

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

Purpose5/5

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

The description clearly states that the tool lists all roles in the Airflow system along with a v1 API scope. This is a specific verb+resource with a clear boundary, distinguishing it from other list tools like list_permissions or list_plugins.

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 tool versus alternatives. The description only states what it does without providing decision criteria or mentioning any related tools that might be preferable in certain contexts.

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

Deploy Server