ui.schema
Since 0.6Changed in next
[editor or disk] Every style property, unit, selector, pseudo-class, role, design token, binding and refusal code the UI supports, from the parser's tables.
READ THIS BEFORE WRITING A SCREEN OR A STYLESHEET: anything not in it is refused with a diagnostic. section: one table. Needs no Play: without one it reads the engine's table, less the project's tokens.
| Title | What the UI supports |
| Mode | |
| Token cost | about 189 tokens (listed only when its toolset is enabled) |
| Toolset | ui |
Arguments
| Argument | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
agent | string | no | The name of the agent making the call, when several agents share one connection: each named agent is its own actor and plays its own game. Leave it out when there is one agent. | ||
section | string | no | One table: properties, tokens, selectors, roles, bindings, hitModes, diagnostics, units, pseudoClasses, refusedProperties; all: every one. Absent: the list, when the whole is large. |
Example
An MCP tools/call with the required arguments (placeholders in angle brackets).
{
"name": "ui.schema",
"arguments": {}
}