Skip to main content
Glama

Upstream.codes

Get Change Request

get_change_request
Read-only

Read a Change Request: description, current version, versions, reviews, checks and merge readiness. Reviews are pinned to a version number.

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": "get_change_request"
  }
}

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

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 safety profile is covered. The description adds one genuinely useful behavioral detail — that reviews are pinned to a version number — but leaves other promised concepts such as 'merge readiness' and 'checks' undefined, and says nothing about authentication scope or behavior when the request number does not exist.

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, front-loaded with the operation and its returned fields, with no filler. The slight redundancy between 'current version' and 'versions' is the only wasted token.

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 no output schema, the description compensates by enumerating the returned data, which is exactly what an agent needs for a read tool with three simple required parameters. Missing only edge-case guidance (not-found handling, permission requirements) for full completeness.

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 67%: owner and repo are documented in the schema, while number carries no description at all. The tool description adds no parameter-level meaning (no format hints, no note that number is the change request index), so it neither compensates for the gap nor duplicates the schema.

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 gives a specific verb ('Read') plus the exact resource ('a Change Request') and enumerates the payload it returns: description, current version, versions, reviews, checks and merge readiness. That is enough to tell it apart from list_change_requests and get_change_request_diff, though it never names those siblings 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?

Usage is only implied: the singular 'a Change Request' plus the required owner/repo/number triple signals a single-record lookup rather than a listing. There is no explicit statement of when to prefer this over get_change_request_diff or list_change_requests, and no stated prerequisites or failure conditions.

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