Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

List pipeline schedules

list_pipeline_schedules
Read-only

List a connected repository's cron schedules: id, cron, timezone, ref, dispatch inputs, whether it is enabled, when it fires next and what it last did. Address the repository with exactly one of repository_id, application_id, or owner and repo. 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_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name, with owner.
ownerNoRepository owner (organisation or user), with repo, instead of repository_id.
providerNoNarrows owner and repo when the same repository is connected on two providers.
repository_idNoThe connected repository's id, from list_pipeline_repositories.
application_idNoAn application whose linked repository to address, instead of repository_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only' plus the required scope 'pipelines.read', which is genuinely useful authorization context not present in the annotations. It does not discuss pagination or result limits, keeping it below a 5.

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 sentences, front-loaded with the resource and returned fields, then the addressing rule and permission. No redundant or filler wording.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields, and it covers addressing, permission scope, and read-only behavior. An agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the mutual-exclusivity constraint ('exactly one of') that the flat schema does not express. That is real meaning beyond the schema, though it does not explain the provider parameter's role.

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?

States a specific verb and resource ('List a connected repository's cron schedules') and enumerates the returned fields (id, cron, timezone, ref, dispatch inputs, enabled, next fire, last result). This clearly separates it from create_pipeline_schedule, update_pipeline_schedule, and delete_pipeline_schedule in the sibling list.

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

Usage Guidelines4/5

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

Gives an explicit addressing rule: 'exactly one of repository_id, application_id, or owner and repo', which tells the agent how to invoke it correctly. It does not name a sibling alternative or state when-not to use it, so it falls short of a 5.

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