Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AVIATOR_DEMONoSet to 1 to run the server on simulated data (no token, no network) for demos.
AVIATOR_API_URLNoBase URL for the Aviator API. Defaults to https://api.aviator.co; set it for on-prem installs.https://api.aviator.co
AVIATOR_API_TOKENNoBearer token for the Aviator API. Create an account token or a personal av_uat_… token in Aviator (Settings → API token).
AVIATOR_DEFAULT_ORGNoDefault organization used when a tool call omits org.
AVIATOR_DEFAULT_REPONoDefault repository used when a tool call omits repo.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

DEMO MODE: all data is simulated (fake org 'acme'); tell the user results are not real. Tools for Aviator MergeQueue (merge queue for GitHub PRs). Every tool takes org and repo (or repo='org/name'). Read state before changing it. Write tools act on the real queue: confirm intent with the user for skip_line, pausing, and config changes. For update_config, call get_config first and send the full edited YAML.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_repositoriesA

List repositories connected to Aviator with paused (whole-repo pause) and active. Branch-level pause state is not readable via Aviator's API.

get_queue_statsA

Live queue depth for a repo: queued, processing and waiting PR counts.

list_queued_prsB

PRs currently in the merge queue, in queue order (number, title, author, status).

get_pr_statusA

Merge-queue status of one PR, looked up by number OR branch (exactly one). Includes its batch (bot) PR, if any.

get_bot_prA

PRs batched into an Aviator bot (draft) PR. Use it when a batch's CI failed, to see which PRs were in it.

get_bisection_statusB

Whether Aviator is bisecting a failed batch containing this PR, and the failing bot PR.

get_configB

Current MergeQueue YAML config of a repo, optionally with change history.

get_analyticsA

Merge-queue analytics for a date range: time in queue, PRs merged, blocked reasons. Returns a summary; daily rows on request.

queue_prC

Add a PR to the merge queue (Aviator merges it once CI passes).

dequeue_prA

Remove a PR from the merge queue (also clears its skip-line options).

refresh_or_sync_prB

refresh: re-evaluate a PR's queue state. sync: update the PR branch with its base branch.

set_queue_pausedB

Pause or resume merging for a whole repo, or only for matching base branches.

backport_prA

Ask Aviator to backport a merged PR onto another branch (it opens a new PR).

update_configA

Replace a repo's MergeQueue YAML config. Call get_config first, edit only what was asked, send the whole file. Parallel mode: merge_rules.merge_mode.type: parallel + merge_mode.parallel_mode.max_parallel_builds / batch_size.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 14 tools

Disambiguation4/5

Most tools target clearly separate concerns (queue ops, PR status, bot/batch inspection, config, analytics, pause). Minor overlap exists between get_bot_pr, get_pr_status, and get_bisection_status, all of which surface batch/bot PR information during failure investigation, and refresh_or_sync_pr bundles two distinct actions into one tool.

Naming Consistency4/5

Nearly all tools follow a consistent snake_case verb_noun pattern (get_pr_status, list_queued_prs, queue_pr, dequeue_pr, update_config). The only deviation is the compound-verb refresh_or_sync_pr, which is readable but breaks the single-verb convention.

Tool Count5/5

14 tools is well within the well-scoped 3-15 range and each tool maps to a distinct merge-queue operation. No evident filler or redundant tools.

Completeness4/5

The surface covers the core lifecycle: queue/dequeue, status inspection, bisection/batch diagnostics, repo listing, queue stats, config get/update, analytics, pause, and backport. Gaps remain around per-PR skip-line/priority options (dequeue mentions clearing them but nothing sets them) and there is no way to inspect individual PR CI checks or batch contents beyond the bot PR summary.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues