Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

List pipeline repositories

list_pipeline_repositories
Read-only

List the repositories connected to Ankra Pipelines in this organisation (and project), newest first: id, provider, owner, name, default branch, linked application, CI cluster override, merge train settings, whether it is connected for Workspaces only, and what the trigger last decided for it. Filter by provider, owner and repo; page with cursor. Read-only; needs pipelines.read.

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

Input Schema

NameRequiredDescriptionDefault
repoNoOnly repositories with this name.
limitNoRepositories per page, 1 to 100 (default 25).
ownerNoOnly repositories of this owner.
cursorNonext_cursor from the previous page.
providerNoOnly repositories on this provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds real context beyond them: the required 'pipelines.read' permission and the 'newest first' ordering. It does not, however, discuss pagination limits beyond the cursor mention or empty-result behavior.

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?

A single dense but front-loaded sentence: resource and scope first, then returned fields, then filtering/paging, then permission. Every clause carries information, though the field enumeration is long and could be trimmed.

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?

There is no output schema, so enumerating returned fields (id, provider, owner, name, default branch, linked application, CI cluster override, merge train settings, workspaces-only flag, trigger decision) is genuinely necessary and done well. Auth requirement and ordering are also covered; only minor gaps remain around pagination behavior.

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%, so the schema already fully documents all five parameters, including the enum and limits. The description only restates the filter and cursor semantics without adding syntax or edge-case detail, so 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 clear verb+resource+scope: 'List the repositories connected to Ankra Pipelines in this organisation (and project)'. This distinguishes it implicitly from the singular get_pipeline_repository and from list_gitops_repositories, but no sibling is named explicitly.

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?

Filtering and paging are described ('Filter by provider, owner and repo; page with cursor'), which implies browsing/listing use. However, there is no explicit when-to-use guidance, no statement on when to prefer get_pipeline_repository for a single repo, and no prerequisites beyond the permission note.

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

All Ankra toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources