Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

List pull requests

devops_pull_request_list
Read-only

List repository pull requests with filters for status, target branch, creation or closing time, and paging; use returned prId for detail lookups.

Instructions

List pull requests of a repository, optionally filtered by status, target branch, and a time range. 'min_time'/'max_time' filter on the creation time by default, or on the closing time when 'time_range_type' is 'closed' (completed pull requests only). Supports paging with 'top' and 'skip'. Use 'devops_pull_request_get' with a returned 'prId' for details.

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": {
      "repository_id": "<repository_id>"
    },
    "name": "devops_pull_request_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of pull requests to return.
skipNoNumber of pull requests to skip (for paging).
statusNoFilter by status: active, abandoned, completed, all, or notSet. The server default is active.
max_timeNoUpper time bound (ISO 8601 date/time), applied as described by time_range_type.
min_timeNoLower time bound (ISO 8601 date/time), applied as described by time_range_type.
repository_idYesRepository name or ID.
target_ref_nameNoFilter by target branch, e.g. 'refs/heads/main'.
time_range_typeNoWhat min_time/max_time refer to: 'created' (default; creation time) or 'closed' (closing time; requires status completed).created

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: paging behavior, the creation-vs-closing time filter switch, and the constraint that closed-time filtering only applies to completed PRs. It does not state default/maximum page sizes or sort order.

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?

Three sentences, each earning its place: scope first, then the nontrivial time-filter rule, then paging and the sibling handoff. Zero filler and no repetition of the tool name or title.

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 an 8-parameter read-only list tool with an output schema, the description covers filtering, paging, and the tricky time-range semantics adequately. Remaining gaps (default page size, sort order, status default already in schema) are minor given the schema and output schema carry the rest.

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 cross-parameter meaning: that 'min_time'/'max_time' bind to creation time by default and to closing time when 'time_range_type' is 'closed', and that closed mode is limited to completed PRs. That interaction is the one thing a flat schema documents least well.

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?

Specific verb and resource ('List pull requests of a repository') plus the filter dimensions it supports (status, target branch, time range). It also distinguishes itself from the sibling detail tool by naming 'devops_pull_request_get' and stating the handoff condition, so an agent can route without opening a 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 clear usage context: paging via 'top'/'skip', time filtering semantics, and the explicit rule that 'time_range_type' of 'closed' returns completed pull requests only. It routes to 'devops_pull_request_get' for details. It lacks explicit when-not-to-use guidance against other listing siblings such as the thread or repository list tools.

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