amendor-mcp

Attach preview URL

set_preview_url

Idempotent

Attach a deploy-preview URL to a change request and mark it ready for requester review.

Instructions

Attach a deploy-preview URL to a change request and mark it ready for the requester to review.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Change request id.
`url`	Yes	Deploy-preview URL (from your host) that the requester will review.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Change request id.
`status`	Yes	New status, set to "preview".
`review_url`	Yes	Page where the requester reviews and approves the change.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.4Jun 22, 2026

addedInput schema / properties / id / description
```
Added value: +"Change request id."
```

addedInput schema / properties / url / description

Added value: +"Deploy-preview URL (from your host) that the requester will review."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Change request id.",
+      "type": "string"
+    },
+    "review_url": {
+      "description": "Page where the requester reviews and approves the change.",
+      "type": "string"
+    },
+    "status": {
+      "description": "New status, set to \"preview\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "status",
+    "review_url"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations indicate idempotent and non-destructive, and description mentions 'mark it ready' as behavioral effect. However, it does not clarify behavior if URL already exists or if change request is not found. Adds some value beyond annotations but incomplete.

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?

Single sentence conveying all necessary information without extraneous words. Well-structured and easy to parse.

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 simple tool with two parameters and output schema present, description covers core purpose and effect. However, missing details like prerequisite (change request must exist) or error cases, mildly reducing completeness.

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 100%, so parameters are documented. Description repeats 'deploy-preview URL' but adds no new semantics beyond the schema, such as constraints on URL format or implications of the id. Baseline score applies.

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?

Description clearly states the action: attaching a deploy-preview URL to a change request and marking it ready for review. It uses specific verb and resources, differentiating from sibling tools like get_change_request (read) and update_status (status change without URL).

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?

No explicit guidance on when to use this tool vs alternatives like update_status. It implies use when attaching a URL, but lacks exclusions or context for when not to use it. Adequate but minimal.

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

Deploy Server