Skip to main content
Glama

Upstream.codes

List Change Request comments

list_change_request_comments
Read-only

List a Change Request's conversation comments and inline review comments.

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

Input Schema

NameRequiredDescriptionDefault
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/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 safety profile is covered. The description adds the useful scope detail that both conversation and inline review comments are returned, but says nothing about pagination, ordering, truncation, or permission requirements on private repos.

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 filler; the resource and both comment categories are stated immediately.

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 list tool with three required params and no output schema, the definition is serviceable but thin: the undocumented number parameter and the absence of any hint about result shape or pagination leave real gaps an agent must discover at call time.

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

Parameters2/5

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

Schema coverage is 67%: owner and repo are documented in the schema, while number has no description at all. The description contributes no parameter meaning — it doesn't clarify that number is the Change Request number rather than an ID — so the documented gap is left unfilled.

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?

Specific verb plus resource: 'List a Change Request's conversation comments and inline review comments.' It even distinguishes two comment categories, which helps an agent understand scope. It doesn't differentiate from siblings (e.g., get_change_request or list_issues), but the resource is unambiguous.

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?

Usage is only implied by the verb 'List'; there is no statement about when to prefer this over get_change_request or list_issues, nor any prerequisites such as needed access to the repo or the Change Request state. An agent can infer intent but gets no explicit routing guidance.

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