Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Remove from merge train

remove_from_merge_train

Take a pull request out of its repository's Ankra merge train, by entry_id or pull_request_number. You must have put it in, or hold the authority an enqueue needs. An entry being merged, or that already left the train, is refused. Address the repository with exactly one of repository_id, application_id, or owner and repo. Needs pipelines.operate.

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

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name, with owner.
ownerNoRepository owner (organisation or user), with repo, instead of repository_id.
entry_idNoThe train entry, from get_merge_train.
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.
pull_request_numberNoThe pull request whose active entry to take out, instead of entry_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the authorization model (must be the enqueuer or hold equivalent authority), the required OAuth scope (pipelines.operate), and the failure modes that are refused. This is exactly the kind of behavioral context annotations cannot carry, and nothing contradicts readOnlyHint=false / destructiveHint=false (the PR itself is untouched).

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?

Five tight sentences, front-loaded with the action and selectors, then prerequisites, then failure modes, then addressing rule and permission. No sentence is padding.

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 7-parameter mutation with no output schema, it covers addressing, authority, and refusal conditions well. Minor gaps: it does not state what a successful call returns or whether the PR is merely dequeued, and it leaves the one-of entry_id/pull_request_number requirement implicit while the schema marks nothing required.

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 baseline is 3, but the description adds a real constraint absent from the schema: the repository must be addressed with exactly one of repository_id, application_id, or owner+repo. It also clarifies entry_id and pull_request_number are interchangeable selectors.

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 ("Take a pull request out of its repository's Ankra merge train") plus the two identifying keys. It is immediately distinguishable from the inverse sibling add_to_merge_train without opening either schema.

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 concrete refusal conditions (entry already merging, or already left the train) and a prerequisite (you must have enqueued it or hold enqueue-level authority). It does not explicitly name add_to_merge_train or get_merge_train as the alternative path, but the context is unambiguous.

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