Skip to main content
Glama

Coline

Show a change request

show_change_request
Read-onlyIdempotent

Shows a change request inside the chat with Coline's Code view: its state, branches, checks and the diff of its changed files. Use it when the person wants to look at or review a change.

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": "show_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
filesYes
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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and a closed world, so the safety profile is fully covered. The description adds value by disclosing what the view surfaces (state, branches, checks, diff), but says nothing about whether the view is transient or persistent for the user, or whether it changes the conversation state. With annotations carrying the safety burden, this is adequate but not rich.

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 sentences, front-loaded with the action and contents, then the usage condition. No filler; the only slightly decorative element is the branded "Coline's Code view" phrasing, which still conveys that this is a UI rendering rather than a raw data response.

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?

For a read-only tool with an output schema, rich annotations, and mostly documented parameters, the description covers what an agent needs in order to call it and to know what the user will see. The remaining gap is sibling differentiation against get_change_request and get_change_request_files, which matters because the catalog contains several near-duplicates.

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?

The description mentions no parameters at all, while schema coverage sits at 67%: workspace and repository are documented but the required `number` is bare. It does not clarify that `number` is the change-request number or that workspace/repository scope the lookup, so it adds nothing beyond the schema and leaves one required field fully undocumented.

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 pairs a specific verb ("Shows") with a specific resource ("a change request") and enumerates what is displayed: state, branches, checks, and changed-file diff. It also names the rendering context ("inside the chat with Coline's Code view"), which separates it from a pure data-fetch tool. However, it never distinguishes itself from the sibling get_change_request, so the agent must infer the difference from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it when the person wants to look at or review a change" gives a clear triggering intent that maps well to review workflows. There is no explicit when-not or named alternative (e.g., get_change_request for programmatic data, get_change_request_files for just files), so the exclusion side is left to inference.

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