Skip to main content
Glama

Coline

List change requests

list_change_requests
Read-onlyIdempotent

Lists a repository's change requests (Upstream's pull requests), newest first: open by default, or closed, merged, drafts or all.

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": {
      "workspace": "<workspace>",
      "repository": "<repository>"
    },
    "name": "list_change_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNoopen
cursorNonextCursor from the previous page.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.

Output Schema

NameRequiredDescriptionDefault
changesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: results are ordered newest first and the default state is open. It says nothing about pagination behavior, result volume, or permission requirements, so it is useful but not rich.

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 front-loaded sentence with no filler; the parenthetical gloss on "pull requests" earns its place by resolving terminology. The colon-separated filter list is dense but readable, and nothing is redundant with the 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?

With an output schema present, return values need no explanation, and the description covers listing scope, ordering, and default filtering for a moderately simple read tool. The remaining gap is that paging behavior and result limits rely entirely on the schema rather than being summarized.

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 60% and the schema already documents workspace, repository, cursor, and enumerates state. The description reinforces the meaning of state (listing the five values and the open default) but adds nothing about limit or cursor semantics, which the schema handles only partially.

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 states a specific verb and resource ("Lists a repository's change requests") and disambiguates the domain term by equating change requests with Upstream's pull requests. It also states ordering (newest first) and the default filter (open), so an agent can distinguish it from the singular get_change_request/show_change_request siblings, even though no sibling is named explicitly.

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

Usage Guidelines3/5

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

It conveys how to use the state filter (open by default, or closed, merged, drafts, all), which is meaningful context. However, it gives no explicit when-to-use versus when-not guidance – nothing about when to prefer get_change_request for a single item, and no note on paging through results with cursor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources