Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Disconnect pipeline repository

disconnect_pipeline_repository
Destructive

Disconnect a repository from Ankra Pipelines: no push, pull request, schedule or merge train starts a run for it any more. Its run history is kept and connecting it again revives it. Refused while a run is queued or running. Address the repository with exactly one of repository_id, application_id, or owner and repo. Needs pipelines.manage.

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": "disconnect_pipeline_repository"
  }
}

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.7/5.0
Behavior5/5

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

Beyond the destructive annotation, the description explains what happens to existing run history, that reconnecting revives the repository, the queued/running precondition, and the required 'pipelines.manage' permission. This is exactly the kind of consequence and prerequisite context an agent needs before invoking a destructive mutation.

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?

The description is front-loaded with the core action and consequences, then moves to preconditions, required addressing form, and permission. Every sentence carries operational value, with no filler.

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?

For a destructive mutation with no output schema, the description covers effects, reversibility, blocking conditions, permission requirements, and address-selection rules. Nothing material is missing for an agent to decide whether and how to call it.

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 useful mutual-exclusivity rule: address the repository with exactly one of repository_id, application_id, or owner and repo. It does not mention the provider parameter, but the schema already documents that option clearly.

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 description uses a specific verb and resource: 'Disconnect a repository from Ankra Pipelines', and immediately defines the scope of the effect across push, pull request, schedule, and merge train triggers. It also distinguishes this operation from reconnecting by noting that history is kept and connecting again revives the repository.

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?

The description gives a clear operational exclusion: it is 'Refused while a run is queued or running.' It also implies the reconnect path by saying connecting again revives the repository, though it does not explicitly name connect_pipeline_repository as the alternative tool.

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