Skip to main content
Glama

get_bisection_status

Read-onlyIdempotent

Determine whether Aviator is bisecting a failed batch containing a given pull request and identify the failing bot PR, helping diagnose blocked merges.

Instructions

Whether Aviator is bisecting a failed batch containing this PR, and the failing bot PR.

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": {
      "number": "<number>"
    },
    "name": "get_bisection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
numberYesPull request number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds what the call actually surfaces (bisection state and the failing bot PR), which is useful beyond the annotations, but it does not say what is returned when no bisection is in progress.

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?

A single compact sentence with the key concept (bisecting a failed batch) front-loaded and no filler. It is a sentence fragment rather than a clean statement of purpose, which slightly hurts readability but not economy.

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

Completeness3/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 bears the burden of describing the response, and it only partly does so: a bisection indicator and the failing bot PR. Missing is the negative case (what is returned when the PR is not in a bisected batch) and any pointer to related tools such as get_bot_pr.

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

Parameters3/5

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

Schema description coverage is 100%, so org, repo and number are fully documented in the schema, including the 'org/name' shorthand and the positive-integer constraint. The description adds nothing about parameters, which is acceptable at full coverage but is baseline only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific query: whether Aviator is bisecting a failed batch that contains the given PR, plus the failing bot PR. That is a concrete verb+resource outcome an agent can recognize. It does not, however, contrast itself with siblings like get_pr_status or get_bot_pr, so the agent must infer the boundary from the name alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of an alternative tool for general PR status. The agent is left to guess that this is a narrow bisection-specific lookup rather than a general status check.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.