Skip to main content
Glama

Coline

Get a change request

get_change_request
Read-onlyIdempotent

Reads one change request: its description, branches, size, reviewers, checks on the current version and what blocks merging.

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

Input Schema

NameRequiredDescriptionDefault
numberYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.

Output Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
fromYes
intoYes
draftYes
stateYes
titleYes
authorYes
checksYes
labelsYes
numberYes
versionYes
blockersYes
canMergeYes
additionsYes
deletionsYes
reviewersYes
updatedAtYes
changedFilesYes

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?

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description adds some behavioral scoping by noting that checks are evaluated 'on the current version' and that merge blockers are surfaced, but it says nothing about lookup failures, missing permissions, or the shape of the response.

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 verb and scope come first and the payload enumeration follows. The field list is dense and partly duplicates what the output schema already conveys, which keeps it just below top marks.

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?

An output schema exists, so return values need not be spelled out, and annotations carry the safety semantics; what remains is a lightweight read tool whose description adequately frames scope. The only real gap is the absence of any guidance on identifiers or failure behavior.

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 67% — workspace and repository carry their own descriptions and provenance hints, while 'number' is an undescribed positive integer. The description adds no parameter-level meaning at all, so it neither compensates for the undocumented 'number' nor improves on 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 opens with a specific verb and resource ('Reads one change request') and then enumerates the concrete payload: description, branches, size, reviewers, checks, and blockers. That makes it clearly distinguishable from a list operation or a files-only read, though it never names a sibling to contrast with.

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 — an agent can infer this is the tool for pulling a single change request's full detail, but there is no explicit 'use this when…' statement, no statement of when to prefer get_change_request_files or list_change_requests, and no preconditions mentioned.

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