Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Enable merge when green

enable_merge_when_green
Destructive

Turn on Merge when green for the GitHub connection a repository is reached through, so scm_merge_pull_request is honoured there. Use it only when github_get_pull_request's next_step offers it: the connection is in Agent mode and merge when green is off, and the user asked Ankra to merge a pull request. The switch is connection-wide, the same one as AI settings, Connections in the portal: it applies to every repository on that GitHub connection, so say that in plain words before proposing it. It never switches a connection from Ask to Agent mode; a connection in Ask mode is refused, and an organisation admin changes that in the portal. Only an organisation admin (ai.manage) may run it. After it succeeds, propose scm_merge_pull_request for the pull request's current head sha. Requires the exact owner and repo from a prior github_list_repositories or github_get_pull_request call - never guess them.

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": {
      "repo": "<repo>"
    },
    "name": "enable_merge_when_green"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name. Also accepts the combined 'owner/name' form.
ownerNoRepository owner (e.g. 'octocat'). May be embedded in 'repo' as 'owner/name'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true and idempotentHint=false; the description goes far beyond by disclosing that the switch is connection-wide and affects every repository on the connection, that it requires org-admin ai.manage, that Ask-mode connections are refused, and that the follow-up step is scm_merge_pull_request against the current head sha. It also instructs the agent to state the connection-wide blast radius in plain words before proposing, which directly explains the destructive scope.

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?

Front-loaded with the action sentence, then precondition, then scope warning, then permissions, then post-condition and parameter sourcing — a logical order with no filler. It is dense and long, and the closing owner/repo sentence could be folded into the precondition, costing a point on tightness.

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 supplies the return-adjacent information an agent needs: success means proposing scm_merge_pull_request for the current head sha. Prerequisites, permissions, refusal behavior, scope, and parameter sourcing are all covered for a two-parameter mutation tool.

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 parameter shapes are already documented. The description still adds meaningful guidance beyond the schema: owner and repo must come from a prior github_list_repositories or github_get_pull_request call and must never be guessed. That is a provenance rule the schema does not encode.

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+resource (turn on Merge when green) and names the exact scope: the GitHub connection a repository is reached through. It also names the sibling it serves (scm_merge_pull_request) and the sibling that gates it (github_get_pull_request), so an agent can place it precisely among 300+ tools.

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

Usage Guidelines5/5

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

Gives an explicit precondition chain: use only when github_get_pull_request's next_step offers it, the connection is in Agent mode with merge-when-green off, and the user asked Ankra to merge a pull request. It also states an exclusion (Ask-mode connections are refused, never upgraded) and names who can fix that, which is more than most definitions provide.

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