diff --git a/assets/js/apitool-methods-ws.js b/assets/js/apitool-methods-ws.js
index 3036a8b7d3..b9cb461613 100644
--- a/assets/js/apitool-methods-ws.js
+++ b/assets/js/apitool-methods-ws.js
@@ -604,7 +604,8 @@ Request('server_state', {
   link: "server_state.html",
   body: {
     "id": 1,
-    "command": "server_state"
+    "command": "server_state",
+    "ledger_index": "current"
   }
 })
 
diff --git a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md
index 76e821fadf..3eafd8efbe 100644
--- a/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md
+++ b/content/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md
@@ -11,6 +11,8 @@ labels:
 
 The `server_state` command asks the server for various machine-readable information about the `rippled` server's current state. The response is almost the same as the [server_info method][], but uses units that are easier to process instead of easier to read. (For example, XRP values are given in integer drops instead of scientific notation or decimal values, and time is given in milliseconds instead of seconds.)
 
+The [Clio server](the-clio-server.html) does not support `server_state` directly, but you can ask for the `server_state` of the `rippled` server that Clio is connected to. Specify `"ledger_index": "current"` (WebSocket) or `"params": [{"ledger_index": "current"}]` (JSON-RPC).
+
 ## Request Format
 An example of the request format:
 
@@ -21,7 +23,8 @@ An example of the request format:
 ```json
 {
   "id": 2,
-  "command": "server_state"
+  "command": "server_state",
+  "ledger_index": "current"
 }
 ```
 
@@ -31,7 +34,7 @@ An example of the request format:
 {
     "method": "server_state",
     "params": [
-        {}
+        {"ledger_index": "current"}
     ]
 }
 ```