Skip to main content
Glama

Coline

Read a change request's files

get_change_request_files
Read-onlyIdempotent

Reads the files a change request changes, with each file's patch, a page at a time. Follow nextCursor for more files.

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_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNonextCursor from the previous page.
numberYes
versionNoA version of the change request; default: its latest.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.

Output Schema

NameRequiredDescriptionDefault
filesYes
truncatedYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are paginated one page at a time and continuation is via nextCursor, plus the payload includes per-file patches. It stops short of noting a default page size or total-count behavior.

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?

Two sentences, both front-loaded with the payload description before the pagination note. No filler, no restatement of the title or annotations.

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 shape need not be explained, and the description still usefully mentions patches and paging. For a 6-parameter read tool it is nearly complete; the only real gap is that limit and version semantics are left entirely to the schema.

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%, with cursor, workspace, repository, and version documented in the schema itself. The description reinforces the cursor parameter's role ('Follow nextCursor') but says nothing about limit (default 30, max 100) or the version parameter that selects a CR revision, leaving that meaning to 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 states a specific verb and resource ('Reads the files a change request changes') and even describes the payload ('each file's patch'), so the agent knows exactly what it gets. It does not name a sibling to distinguish itself from, e.g. get_code_diff or read_file, which keeps it just below a 5.

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 only guidance is the pagination instruction 'Follow nextCursor for more files', which tells the agent how to continue but not when to choose this tool over get_code_diff, read_file, or get_change_request. Usage context is implied by the resource name rather than stated.

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