Skip to main content
Glama

Upstream.codes

List Change Requests

list_change_requests
Read-only

List a repository's Change Requests (Upstream's pull requests), open by default.

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

Input Schema

NameRequiredDescriptionDefault
baseNoTarget branch.
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).
stateNo
authorNo
cursorNonextCursor from a previous page.
perPageNoResults per page (default 30).

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 and openWorldHint=true, so the read-only, remote-data nature is known without the description. The description adds one piece of behavior beyond that: the default state filter is 'open'. It says nothing about pagination (despite cursor/perPage existing) or about how large result sets are returned.

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?

A single front-loaded sentence with no waste; the scope ('a repository's') and the domain gloss are placed before the default-behavior note. Nothing redundant or padded.

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 is the only place to learn what the listing returns and how to page through it, and it omits both, along with any mention of the author filter. For a 7-parameter, paginated listing tool it is adequate but leaves real gaps.

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 71%, so owner, repo, base, cursor and perPage are largely documented in the schema itself. The description adds meaning only for state ('open by default'), while author and the filter combinations (state=drafts, merged, etc.) are left entirely to the schema. This is a baseline-appropriate contribution rather than compensating detail.

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?

States a specific verb (List) and resource (a repository's Change Requests) and clarifies the domain synonym by equating them with Upstream's pull requests, so an agent knows what is being enumerated. It does not explicitly differentiate itself from get_change_request or list_change_request_comments, but the verb/resource pairing is unambiguous on its own.

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?

The phrase 'open by default' implies the default scope and hints that the tool is for browsing rather than fetching a single item, which lightly separates it from get_change_request. There is no explicit when-to-use versus alternatives statement (e.g., use search_issues-like filtering, or use get_change_request for a single CR), so guidance remains implied.

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