Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

list_roles

Retrieve all Airflow roles via the v1 API, using limit and offset for pagination, to inspect access-control roles.

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

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 20.
offsetNoNumber of records to skip for pagination. Default: 0.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.7.4
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records to request per page. Default:\n20."
    • addedInput schema / properties / offset / description
      Added value: +"Number of records to skip for pagination. Default: 0."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed3 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
  5. Addedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It makes clear this is a read-style listing operation and adds the v1-only constraint, but it does not disclose authorization requirements, rate limits, or whether the result is paginated beyond the presence of limit/offset in the schema.

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 front-loaded sentence with no wasted text. The bracketed label is minor and does not obscure the core 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 and fully documented pagination parameters, the description is mostly sufficient. However, the absence of annotations and the lack of guidance on when to use this versus related list tools leave some contextual gaps.

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 both limit and offset are documented with defaults in the schema. The description adds no additional parameter semantics, so the schema does the heavy lifting and baseline 3 is appropriate.

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?

The description states a specific verb and resource: it lists all roles in the Airflow system. It also scopes the tool to the v1 API only, making the purpose clear, though it does not explicitly distinguish itself from siblings like list_permissions or list_users.

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 only usage context is the 'v1 API only' constraint. The description gives no guidance on when to choose this tool over related sibling tools such as list_permissions, and no prerequisites or exclusions are stated.

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