A2UI Atomic Catalog

deck_build

Idempotent

Build a PowerPoint (.pptx) file from a scene list or an A2UI payload. Deterministic (same input, same bytes), nothing is stored or fetched, text is fitted with real font metrics and the file is linted (overlap, bounds, contrast, alt text). Returns the file as an embedded resource plus a report: errors, lint, warnings and unsupported atoms. Opens in PowerPoint and Google Slides (checked in Google Slides). Demo limit: 10 builds a day per connection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deck_build"
  }
}

Input Schema

Name	Required	Description
`deck`	No	A typed scene list: {"title","target","scenes":[{"type":"title\|bullets\|stats\|quote\|table\|media\|cta","f":{...fields...},"notes":"speaker notes"}]}. Same scene fields as make_film (eyebrow, headline, sub, kicker, stats as [value,label] pairs, steps/items, quote, name, role, b1/l1, foot). Call deck_schema for every layout and limit. Give deck OR payload.
`target`	No	Where the file will be opened. google-slides fits text tighter; powerpoint and any keep a 12% margin for a substituted font. Default any. Ask the user if you do not know.
`payload`	No	An A2UI payload {"blocks":[{"type":"quote",...},...]}: each atom with a slide recipe becomes slides, others are listed under `unsupported`, never guessed. deck_schema lists the atoms. Give payload OR deck.
`delivery`	No	How the .pptx comes back. link (default): a download link valid for one hour, which works in every client including chat apps that cannot receive attachments. file: the .pptx as an embedded resource, for clients that save attachments (Claude Desktop, Claude Code). both: the two together.
`skip_film_only`	No	For a scene list that came from a film: leave out scenes with no slide layout (chart, chat, word, morph, captions, image) instead of treating them as errors.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes well beyond the annotations: determinism ('same input, same bytes'), no storage or fetching, font-metric fitting, lint categories, a per-connection rate limit of 10 builds/day, and cross-app compatibility. However, it says the file 'returns as an embedded resource' while the delivery parameter declares 'link' as the default, so the actual default return channel is stated two conflicting ways.

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 action and artifact, then behavior, then return shape, then limits — a sensible order with little filler. The one flaw is the return-channel sentence, which conflicts with the delivery default and forces the reader to reconcile it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly spells out the return payload (file plus errors, lint, warnings, unsupported atoms) and discloses the demo quota and compatibility guarantees. The only gap is the unresolved ambiguity about whether the default delivery is a link or an embedded resource.

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% and every parameter already carries a detailed description, so the schema does the heavy lifting. The prose adds no parameter-level meaning beyond the schema; it only restates that deck or payload must be supplied.

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 artifact ('Build a PowerPoint (.pptx) file') plus the two accepted input forms (scene list or A2UI payload). It also routes the agent to deck_schema for layouts, so the agent can tell this apart from the schema/validate siblings 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 Guidelines4/5

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

Gives concrete routing ('Call deck_schema for every layout and limit'), an either/or on inputs ('Give deck OR payload'), and a conditional escape hatch ('skip_film_only ... instead of treating them as errors'). It lacks explicit when-not guidance relative to deck_validate, which is the obvious adjacent tool.

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

All A2UI Atomic Catalog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.