Amendor

Get change request

get_change_request

Read-onlyIdempotent

Get full detail for one change request so you can implement it: the user request, the exact element they pointed at (CSS selector + outerHTML), the page URL, and a screenshot URL. Call this before making the 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": {
      "id": "<id>"
    },
    "name": "get_change_request"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Ticket code like "RB-3" from list_change_requests (raw ids also work).

Output Schema

Name	Required	Description
`id`	Yes	Internal change request id (used in branch names and PR markers).
`code`	Yes	Short ticket code.
`status`	Yes	Current status.
`elements`	Yes	Elements attached to the request; empty for a general request.
`page_url`	Yes	URL of the page the request was made on.
`request_text`	Yes	What the user wants.
`requested_by`	Yes	Requester email, or "anonymous".
`screenshot_url`	Yes	Absolute screenshot URL, or empty string.
`attachment_urls`	Yes	Absolute URLs of any extra attachments.
`revision_comment`	Yes	The revision note, or empty string if none.
`revision_requested`	Yes	True if the requester reviewed a preview and asked for changes; push to the same branch/PR.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 19, 2026

changedInput schema / properties / id / description

Previous value: -"Change request id, from list_change_requests."New value: +"Ticket code like \"RB-3\" from list_change_requests (raw ids also work)."

addedOutput schema / properties / code

Added value: +{
+  "description": "Short ticket code.",
+  "type": "string"
+}

changedOutput schema / properties / id / description

Previous value: -"Change request id."New value: +"Internal change request id (used in branch names and PR markers)."

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "page_url",
-  "requested_by",
-  "request_text",
-  "revision_requested",
-  "revision_comment",
-  "elements",
-  "screenshot_url",
-  "attachment_urls"
-]New value: +[
+  "code",
+  "id",
+  "status",
+  "page_url",
+  "requested_by",
+  "request_text",
+  "revision_requested",
+  "revision_comment",
+  "elements",
+  "screenshot_url",
+  "attachment_urls"
+]

First observedJun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds useful context beyond annotations by specifying exactly what data is returned (user request, element, page URL, screenshot URL), which helps the agent understand the tool's output without relying solely on the output schema.

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?

The description is two sentences, immediately states the purpose, and lists specific data fields without unnecessary detail. Every word earns its place, making it highly concise and well-structured.

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 a simple one-parameter tool, a rich output schema, and strong annotations, the description covers all essential aspects: what the tool does, what it returns, and when to call it. The only minor omission is lack of explicit mention that no user/workspace filtering applies (though that's not relevant here). It is nearly complete.

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?

The input schema has 100% coverage, with the parameter 'id' fully described as a ticket code like 'RB-3' from list_change_requests. The description does not add additional parameter information, which is acceptable since the schema already carries the burden. The baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves full detail for a single change request, specifically listing the fields (user request, element selector, outerHTML, URLs). It distinguishes from siblings like list_change_requests by emphasizing 'one change request' and 'full detail'.

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?

The description provides explicit guidance: 'Call this before making the change.' This implies it should be used before mutation tools like update_status. While it doesn't explicitly state when not to use it, the context of implementation is clear. Also references list_change_requests for obtaining the id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Amendor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.