Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Create pipeline schedule

create_pipeline_schedule

Create a cron schedule that starts a connected repository's Ankra pipeline. cron is a five-field expression evaluated in timezone (default UTC); ref is the branch or tag it runs at; inputs are the pipeline's on.manual.inputs. A schedule is created enabled unless enabled is false. Refused for a repository connected for Workspaces only. Address the repository with exactly one of repository_id, application_id, or owner and repo. Needs pipelines.manage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cron": "<cron>"
    },
    "name": "create_pipeline_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoBranch or tag the scheduled runs run at.
cronYesFive-field cron expression, for example 0 3 * * *.
repoNoRepository name, with owner.
ownerNoRepository owner (organisation or user), with repo, instead of repository_id.
inputsNoDispatch inputs by name, as the pipeline's on.manual.inputs declares them; every value is a string.
enabledNofalse creates it disabled (default true).
providerNoNarrows owner and repo when the same repository is connected on two providers.
timezoneNoIANA timezone the expression is read in (default UTC).
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.4/5.0
Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-idempotent, non-destructive), the description discloses the default-enabled state, the permission requirement, and a rejection condition. It does not mention what happens when a duplicate schedule for the same cron/ref already exists, leaving the non-idempotent behavior unexplained.

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?

Six short clauses, all front-loaded and each carrying distinct information (defaults, exclusion, addressing rule, permission). Nothing is repeated from the name or title.

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 10-parameter mutation tool with a nested inputs object and no output schema, the description covers defaults, addressing rules, permissions, and refusal conditions. The return value (e.g. a schedule id) is unaddressed and there is no output schema to fill that gap.

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 a genuine cross-parameter rule not visible per-property: exactly one of repository_id, application_id, or owner+repo. It also ties inputs to the pipeline's on.manual.inputs contract, adding meaning beyond the schema text.

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?

The first sentence gives a precise verb+resource+effect: creates a cron schedule that starts a connected repository's Ankra pipeline. It is clearly distinguishable from update_pipeline_schedule, list_pipeline_schedules, and run_pipeline 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?

It states prerequisites (pipelines.manage), an explicit exclusion (refused for repositories connected for Workspaces only), and the three mutually exclusive ways to address the repository. It does not name the sibling to use for editing or listing schedules, which keeps it 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