Skip to main content
Glama

Coline

Open a draft change request

open_code_change_request
Idempotent

Opens a draft change request on Upstream with a Code session's changes, for the team to review.

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>",
      "sessionId": "<sessionId>"
    },
    "name": "open_code_change_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesCode session id from list_code_sessions.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
planYes
taskYes
stateYes
checksYes
projectYes
sessionIdYes
previewUrlYes
statusLineYes
changeRequestUrlYes

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 cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false). The description adds genuinely useful context beyond them: the request is created as a DRAFT, not a final review request, and its content comes from an existing code session. It does not explain what a repeat call does given idempotency, or whether any permission on the upstream repo is required.

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 that names the action, target, source, and audience with no filler or repetition of the title. Nothing could be removed without losing meaning.

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?

An output schema exists, so return values need no explanation, and the two required parameters are fully documented. However, for a mutating tool the description leaves open what a draft change request means downstream (visible to whom, whether it can be promoted or discarded) and what happens when a request already exists, which the idempotent hint implies is survivable.

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 100%, with both parameters documented and cross-referenced to list_code_sessions and workspaces.list, so the baseline of 3 applies. The phrase "a Code session's changes" reinforces that sessionId is the change source but adds no format or constraint detail beyond 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 ("Opens a draft change request on Upstream") plus its input source ("a Code session's changes") and purpose ("for the team to review"). That distinguishes it from read-only siblings like get_change_request or show_change_request, though it never names an alternative 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 implied by "with a Code session's changes" and "for the team to review" — an agent can infer this is the step after a code session produces work worth reviewing. There is no explicit statement of prerequisites, no when-not-to-use case, and no pointer to a sibling such as list_change_requests for checking whether one already exists.

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