Compose Preview Catalogs

ui_builder_await_decision

Wait for somebody to approve or reject a design, rather than asking again whether they have. Returns as soon as a decision lands after afterSequence — by default only a person's (from: "human"), on any revision unless you name one — or a timedOut reply after waitSeconds. Every reply carries latest (the newest matching verdict, new or not) and approved, so waitSeconds: 0 is a cheap, idempotent poll for a routine that can only check back later; quote the reply's sequence as the next afterSequence. People record theirs over the design's decisions HTTP route.

Input Schema

TableJSON Schema

Name	Required	Description
`from`	No	Whose decisions count. Defaults to human.
`token`	No	A grant token from poll_access, when you cannot set the X-Compose-Preview-Token header yourself — an MCP client fixes its headers at connect time, so this is how a token approved during this session is used in it. Prefer the header where you control it.
`designId`	Yes
`revision`	No	Only decisions on this revision.
`agentName`	No	Optional agent/client name shown to design viewers; self-reported.
`agentModel`	No	Optional current model name shown to design viewers; self-reported. Omit when unknown.
`waitSeconds`	No	Up to 120. Defaults to 25; 0 checks without blocking.
`afterSequence`	No	The `sequence` you last saw. 0 for anything at all.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`latest`	No
`schema`	Yes
`summary`	Yes
`approved`	Yes
`designId`	Yes
`sequence`	Yes
`timedOut`	Yes
`decisions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / agentModel

Added value: +{
+  "description": "Optional current model name shown to design viewers; self-reported. Omit when unknown.",
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / agentName

Added value: +{
+  "description": "Optional agent/client name shown to design viewers; self-reported.",
+  "maxLength": 80,
+  "type": "string"
+}

AddedOct 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses the timeout behavior (`timedOut` reply after `waitSeconds`), the default filter (`from: "human"`), that `latest` may be a previously seen verdict, and the auth workaround for header-fixed MCP clients. This is unusually rich behavioral context.

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 purpose and the polling caveat; nearly every clause carries information. It is a dense, em-dash-heavy paragraph, but not padded — a mild deduction only for density that makes it slightly harder to scan.

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 an 8-parameter blocking tool with an output schema, the description covers the essentials: blocking semantics, defaults, timeout result, return fields, and how to chain calls. Nothing an agent needs to invoke it correctly is missing.

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 88%, so the schema already documents most parameters. The description still adds value by tying parameters together operationally — the `afterSequence`/`sequence` loop, the default human filter, and `waitSeconds: 0` polling semantics — rather than merely restating field docs.

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?

States a specific verb and resource ('Wait for somebody to approve or reject a design') and immediately contrasts it with the naive alternative ('rather than asking again whether they have'). An agent can distinguish it from siblings like ui_builder_check_design or ui_builder_await_comments without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it (waiting for a verdict instead of re-asking) and names the concrete degenerate mode ('waitSeconds: 0 is a cheap, idempotent poll for a routine that can only check back later'). The continuation pattern ('quote the reply's `sequence` as the next `afterSequence`') gives the agent the loop contract.

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

All Compose Preview Catalogs tools Inspect

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.