Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)

Wait for the user's pick

wait_for_pick

Read-only

Wait for the person to choose on the pick page. Long-polls up to 50 seconds and returns as soon as they click, or status "pending" (call again). Once chosen: their reference with its screenshot attached and a full build prompt. "dismissed" means none fit: ask what they want. A pick can be collected for 24 hours.

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": {
      "pickId": "<pickId>"
    },
    "name": "wait_for_pick"
  }
}

Input Schema

Name	Required	Description	Default
`wait`	No	Seconds to wait for a choice, 0 to 50.
`pickId`	Yes	The pickId returned by pick_reference.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 30, 2026

changedInput schema / properties / pickId / description

Previous value: -"The pickId returned by pickReference."New value: +"The pickId returned by pick_reference."

addedInput schema / properties / wait / maximum
```
Added value: +50
```
addedInput schema / properties / wait / minimum
```
Added value: +0
```

changedInput schema / properties / wait / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "choice": {
-      "properties": {
-        "actions": {
-          "items": {
-            "properties": {
-              "label": {
-                "type": "string"
-              },
-              "region": {
-                "description": "Hotspot position as percentages of the image.",
-                "properties": {
-                  "height": {
-                    "type": "number"
-                  },
-                  "width": {
-                    "type": "number"
-                  },
-                  "x": {
-                    "type": "number"
-                  },
-                  "y": {
-                    "type": "number"
-                  }
-                },
-                "type": "object"
-              },
-              "to": {
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "branch": {
-          "type": "boolean"
-        },
-        "captured": {
-          "format": "date",
-          "type": "string"
-        },
-        "height": {
-          "type": "integer"
-        },
-        "id": {
-          "type": "string"
-        },
-        "imageUrl": {
-          "type": "string"
-        },
-        "kind": {
-          "description": "flow is an onboarding step, marketing a public web page, product an in-app screen.",
-          "enum": [
-            "flow",
-            "marketing",
-            "product"
-          ],
-          "type": "string"
-        },
-        "notes": {
-          "type": "string"
-        },
-        "previewUrl": {
-          "type": "string"
-        },
-        "product": {
-          "type": "string"
-        },
-        "productName": {
-          "description": "Present on pick options and related screens.",
-          "type": "string"
-        },
-        "scope": {
-          "description": "What was captured. marketing: logged-out marketing pages only. public-demo: logged out, but real\nproduct surfaces or public demos were used. task-incomplete: signed in, but the journey stops before\nits result. signed-in: signed in, and the journey reaches its result.\n",
-          "enum": [
-            "marketing",
-            "public-demo",
-            "task-incomplete",
-            "signed-in"
-          ],
-          "type": "string"
-        },
-        "sections": {
-          "items": {
-            "properties": {
-              "title": {
-                "type": "string"
-              },
-              "y": {
-                "type": "integer"
-              }
-            },
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "source": {
-          "type": "string"
-        },
-        "style": {
-          "description": "What the screen looks like, judged from its first viewport (tags/style-spec.md). Searchable through q.",
-          "properties": {
-            "accentHue": {
-              "description": "The accent hue of buttons and highlights, or none.",
-              "type": "string"
-            },
-            "aesthetic": {
-              "description": "One or two of minimal, editorial, playful, technical, glassy, bold, warm, data-dense, retro, corporate.",
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "caption": {
-              "description": "What makes the screen look the way it does.",
-              "type": "string"
-            },
-            "colorMode": {
-              "enum": [
-                "monochrome",
-                "single-accent",
-                "multi-color",
-                "pastel",
-                "vivid-gradient"
-              ],
-              "type": "string"
-            },
-            "density": {
-              "enum": [
-                "airy",
-                "balanced",
-                "dense"
-              ],
-              "type": "string"
-            },
-            "headingFont": {
-              "enum": [
-                "sans",
-                "serif",
-                "mono",
-                "rounded",
-                "display"
-              ],
-              "type": "string"
-            },
-            "imagery": {
-              "description": "One or two of none, product-ui, photography, illustration, 3d, icons-only, charts.",
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "theme": {
-              "enum": [
-                "light",
-                "dark",
-                "mixed"
-              ],
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "tags": {
-          "description": "Design-problem tags. The first pattern is the primary one. See listTags.",
-          "properties": {
-            "component": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "pattern": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "state": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "task": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            }
-          },
-          "type": "object"
-        },
-        "title": {
-          "type": "string"
-        },
-        "width": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "message": {
-      "type": "string"
-    },
-    "pickId": {
-      "type": "string"
-    },
-    "prompt": {
-      "description": "Build prompt for the chosen reference.",
-      "type": "string"
-    },
-    "status": {
-      "enum": [
-        "pending",
-        "chosen",
-        "dismissed"
-      ],
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedOct 25, 2026

addedOutput schema / properties / choice / properties / style

Added value: +{
+  "description": "What the screen looks like, judged from its first viewport (tags/style-spec.md). Searchable through q.",
+  "properties": {
+    "accentHue": {
+      "description": "The accent hue of buttons and highlights, or none.",
+      "type": "string"
+    },
+    "aesthetic": {
+      "description": "One or two of minimal, editorial, playful, technical, glassy, bold, warm, data-dense, retro, corporate.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "caption": {
+      "description": "What makes the screen look the way it does.",
+      "type": "string"
+    },
+    "colorMode": {
+      "enum": [
+        "monochrome",
+        "single-accent",
+        "multi-color",
+        "pastel",
+        "vivid-gradient"
+      ],
+      "type": "string"
+    },
+    "density": {
+      "enum": [
+        "airy",
+        "balanced",
+        "dense"
+      ],
+      "type": "string"
+    },
+    "headingFont": {
+      "enum": [
+        "sans",
+        "serif",
+        "mono",
+        "rounded",
+        "display"
+      ],
+      "type": "string"
+    },
+    "imagery": {
+      "description": "One or two of none, product-ui, photography, illustration, 3d, icons-only, charts.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "theme": {
+      "enum": [
+        "light",
+        "dark",
+        "mixed"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 22, 2026

changedOutput schema / properties / choice / properties / productName / description

Previous value: -"Present on pick options."New value: +"Present on pick options and related screens."

addedOutput schema / properties / choice / properties / scope

Added value: +{
+  "description": "What was captured. marketing: logged-out marketing pages only. public-demo: logged out, but real\nproduct surfaces or public demos were used. task-incomplete: signed in, but the journey stops before\nits result. signed-in: signed in, and the journey reaches its result.\n",
+  "enum": [
+    "marketing",
+    "public-demo",
+    "task-incomplete",
+    "signed-in"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / choice / properties / tags

Added value: +{
+  "description": "Design-problem tags. The first pattern is the primary one. See listTags.",
+  "properties": {
+    "component": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pattern": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "state": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "task": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "choice": {
+      "properties": {
+        "actions": {
+          "items": {
+            "properties": {
+              "label": {
+                "type": "string"
+              },
+              "region": {
+                "description": "Hotspot position as percentages of the image.",
+                "properties": {
+                  "height": {
+                    "type": "number"
+                  },
+                  "width": {
+                    "type": "number"
+                  },
+                  "x": {
+                    "type": "number"
+                  },
+                  "y": {
+                    "type": "number"
+                  }
+                },
+                "type": "object"
+              },
+              "to": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "branch": {
+          "type": "boolean"
+        },
+        "captured": {
+          "format": "date",
+          "type": "string"
+        },
+        "height": {
+          "type": "integer"
+        },
+        "id": {
+          "type": "string"
+        },
+        "imageUrl": {
+          "type": "string"
+        },
+        "kind": {
+          "description": "flow is an onboarding step, marketing a public web page, product an in-app screen.",
+          "enum": [
+            "flow",
+            "marketing",
+            "product"
+          ],
+          "type": "string"
+        },
+        "notes": {
+          "type": "string"
+        },
+        "previewUrl": {
+          "type": "string"
+        },
+        "product": {
+          "type": "string"
+        },
+        "productName": {
+          "description": "Present on pick options.",
+          "type": "string"
+        },
+        "sections": {
+          "items": {
+            "properties": {
+              "title": {
+                "type": "string"
+              },
+              "y": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "source": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "width": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "pickId": {
+      "type": "string"
+    },
+    "prompt": {
+      "description": "Build prompt for the chosen reference.",
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "pending",
+        "chosen",
+        "dismissed"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations: it discloses a 50-second long-poll timeout, the return-as-soon-as-they-click semantics, the three outcome states, and a 24-hour collection window. That is exactly the operational context an agent needs to drive a polling loop correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and dense with useful outcome routing in a few sentences, with no filler. Line breaks in the middle of sentences make it slightly harder to scan but nothing is wasted.

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?

There is no output schema, so the description must describe returns, and it does: the chosen reference with attached screenshot, the build prompt, and the pending/dismissed states. Combined with the 24-hour window, an agent has everything needed to call it and interpret results.

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%, with the wait parameter documented as 0–50 seconds and pickId tied to pick_reference, so the schema carries the meaning. The description only restates the 50-second cap and adds no format or edge-case detail (e.g. wait=0 behavior), which lands at the baseline.

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?

States a specific verb and resource: waits for the person's choice on a pick page, returning their reference, screenshot and build prompt. The purpose is unambiguous, but the description never names a sibling; the coupling to pick_reference is only visible in the schema's pickId text, so an agent must read structured fields to differentiate.

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?

Gives clear follow-up behavior for each outcome: 'pending' means call again, 'dismissed' means ask what they want, and a filled pick yields the reference plus build prompt. It doesn't state when not to use it or propose an alternative tool, but the polling loop is well specified.

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

All Screenrove: UI Design Reference & Screenshots (free Mobbin alternative) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?