Skip to main content
Glama
Sign In

Amendor

by io.github.deslay1
OverviewDiscussionsAdmin

List change requests

list_change_requests
Read-onlyIdempotent

List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_change_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOptional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request.

Output Schema

NameRequiredDescriptionDefault
requestsYesMatching change requests, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / requests / items / properties / code
      Added value: +{
+  "description": "Short ticket code like \"RB-3\"; pass to get_change_request.",
+  "type": "string"
+}
    • removedOutput schema / properties / requests / items / properties / id
      Removed value: -{
-  "description": "Change request id; pass to get_change_request.",
-  "type": "string"
-}
    • addedOutput schema / properties / requests / items / properties / project
      Added value: +{
+  "description": "Project the request belongs to.",
+  "type": "string"
+}
    • changedOutput schema / properties / requests / items / required
      Previous value: -[
-  "id",
-  "status",
-  "request_text",
-  "page_url"
-]New value: +[
+  "code",
+  "status",
+  "request_text",
+  "page_url",
+  "project"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds context about the source of the requests ('submitted by end users') but does not disclose additional behavioral details like pagination or ordering, which are not required given the output schema exists and annotations are strong.

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 three short, focused sentences: purpose, filter option, and usage hint. Every sentence earns its place with no redundancy or fluff. The most important info (what it does) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter, full schema description, output schema present, and strong annotations, the description provides enough context. It states what the tool returns, how to filter, and when to use it. No critical gaps remain.

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 only parameter 'status' has 100% schema coverage with a clear description of accepted values and behavior when omitted. The description simply repeats 'Optionally filter by status' without adding new semantic detail, so it adds minimal value beyond the schema.

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 lists change requests with specific context (submitted by end users on sites you ship). The verb 'List' plus resource 'change requests' makes the function unambiguous and differentiates it from sibling tools like get_change_request (single item), set_preview_url, and update_status.

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 phrase 'Start here to see what people are asking for' gives clear usage context as an entry point for exploring change requests. It also mentions the optional status filter, implying the tool is for broad listing. However, it does not explicitly contrast with sibling tools or say when not to use it.

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

All Amendor toolsInspect
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.

Resources