Skip to main content
Glama

Screenrove

by com.screenrove
OverviewDiscussionsAdmin

Build an agent handoff prompt

build_handoff
Read-only

Generate a complete build prompt for a coding agent: ordered screens with notes, observed transitions, full-resolution image URLs, the measured design guide, and an implementation checklist. This is the same prompt as the "Use in agent" button on the site.

Reference IDs: use {product}-onboarding for a product's signup flow, {product}-collection for all their screens, or any single screen id (like linear-marketing-pricing).

Use this when you want to build UI that follows a real product's patterns. The prompt includes everything an agent needs: screenshots to reference, design tokens to match, and implementation steps to follow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoWhat you want to build. Goes at the top of the prompt.
stackNoPreferred stack, e.g. Next.js and Tailwind.
screensNoComma-separated screen ids to keep. Omit to include every screen in the reference.
referenceIdYese.g. linear-onboarding, stripe-collection or vercel-marketing-pricing.
includeDesignNoInclude the observed design guide. Set false to use your project's own design system.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptNoMarkdown prompt to follow or paste into an agent.
manifestNoVersioned reference manifest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "manifest": {
+      "description": "Versioned reference manifest",
+      "type": "object"
+    },
+    "prompt": {
+      "description": "Markdown prompt to follow or paste into an agent.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing exactly what the generated artifact contains (screens, transitions, image URLs, design guide, checklist) and noting the includeDesign toggle's effect on output. It stops short of stating size limits or output format details.

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?

Purpose is front-loaded and the three paragraphs are logically ordered (what it produces, reference IDs, when to use). Slight redundancy exists: the contents are enumerated in paragraph one and restated as 'screenshots to reference, design tokens to match, and implementation steps to follow' in the closing sentence.

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?

An output schema exists, so the description needn't document return values; annotations cover safety; and the schema fully documents all five parameters. Combined with the reference-ID guidance and the when-to-use statement, an agent has everything needed to invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes further by documenting the referenceId naming conventions ({product}-onboarding, {product}-collection, single screen id), which the schema only illustrates with flat examples. It adds real meaning over the structured fields for the required parameter.

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 (generate) and resource (a complete build prompt for a coding agent) and enumerates the concrete contents: screens with notes, transitions, full-resolution image URLs, design guide, and checklist. It distinguishes itself via 'the same prompt as the "Use in agent" button on the site,' though it never explicitly contrasts with siblings like get_design or get_flow.

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 a clear triggering condition: 'Use this when you want to build UI that follows a real product's patterns.' It also explains the reference ID scheme for selecting scope. However, it names no alternatives (e.g. get_design, get_screen) and offers no explicit when-not guidance.

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

All Screenrove toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources