Skip to main content
Glama

get_bot_pr

Read-onlyIdempotent

Retrieve the Aviator bot PR for a failed batch to identify which pull requests were included, helping diagnose CI failures.

Instructions

PRs batched into an Aviator bot (draft) PR. Use it when a batch's CI failed, to see which PRs were in it.

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_bot_pr"
  }
}

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

A3.6/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 useful context that the target is a bot-generated draft PR and that its typical use is post-CI-failure triage. It says nothing about what happens when the number is not a bot PR, or about the shape/volume of results.

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?

Two short sentences with no filler, and the usage condition follows immediately after the purpose. The first sentence is a bare fragment, which costs a little clarity but not length.

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?

For a simple read-only lookup with full schema coverage, full annotations, and no output schema, this is adequate. It still omits the return shape (e.g., PR numbers/titles and whether members are paginated) and error behavior for non-bot PRs, which would matter during CI-failure triage.

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 coverage is 100%, so org, repo, and number are fully documented, giving a baseline of 3. The description only indirectly clarifies that number refers to the bot PR, adding marginal meaning over the schema; it does not restate or enrich parameter formats.

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 the resource precisely: the PRs batched into an Aviator bot (draft) PR, which distinguishes it from status/queue siblings. It is phrased as a noun fragment rather than a verb+resource ('get/list'), and it does not explicitly state that the supplied PR number identifies the bot PR rather than a member PR, leaving a small ambiguity.

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?

'Use it when a batch's CI failed, to see which PRs were in it' gives a concrete trigger condition, which is more than most definitions offer. It does not name an alternative or exclusion (e.g., when to prefer get_pr_status), so the agent must infer the boundary from sibling behavior.

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