Skip to main content
Glama

list_repositories

Read-onlyIdempotent

Lists repositories connected to Aviator and shows whether each is active or paused, helping you find repos with a whole-repo pause. Branch-level pause state is not included.

Instructions

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

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_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds genuine context: it defines what 'paused' means (whole-repo) and discloses a hard API limitation around branch-level pause state. It omits any mention of the limit parameter, ordering, or result size.

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?

Two short sentences, front-loaded with the core action and followed by the scope caveat. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with one optional parameter and no output schema, the description is nearly sufficient, clarifying return fields and a key limitation. The remaining gap is pagination/limit behavior, which matters for an agent deciding how to enumerate all repositories.

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?

There is one parameter (limit) with 0% schema description coverage, so the description carries the burden — but it never mentions the parameter at all. The schema only supplies default 50 and bounds 1-200; no meaning, pagination behavior, or effect of limit is added by the description.

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 names a specific verb and resource ('List repositories connected to Aviator') and even enumerates the pause-state fields returned ('paused', 'active'). It is clearly distinguishable from siblings like list_queued_prs or set_queue_paused, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the tool for inspecting which repos exist and whether they are paused. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for branch-level information beyond the note that it is unavailable via API.

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