Skip to main content
Glama
Sign In

A2UI Atomic Catalog

by ai.a2uicatalog
OverviewDiscussionsAdmin

deck_validate

Read-onlyIdempotent

Check a deck (scene list or A2UI payload) without building it. Returns every error with its slide, field and exact limit, warnings (no speaker notes, no link) and, for a payload, which atoms have no slide recipe. Not rate-limited.

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_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNoA 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.
payloadNoAn 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.
skip_film_onlyNoFor 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.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses the return contents precisely: errors carry slide, field and exact limit; warnings cover missing speaker notes and links; unsupported atoms are listed rather than guessed. The 'Not rate-limited' note is operational context an agent cannot get from annotations or schema.

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

Conciseness5/5

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

Four short sentences, front-loaded with the core verb and the build contrast, then the return contract, then a one-clause operational note. No filler and nothing repeated.

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 carry the return contract, and it does: error granularity, warning categories, and the `unsupported` list for payloads. It also points to deck_schema for layout and limit details and explains the skip_film_only escape hatch, leaving nothing an agent needs before calling.

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 description coverage is 100% and the schema text already explains the scene list shape, the payload shape, and skip_film_only. The description reinforces the mutual exclusivity ('Give deck OR payload') and the no-guessing rule for payload atoms, but adds little field-level meaning the schema does not already carry.

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 (Check) and resource (deck: scene list or A2UI payload), and immediately contrasts with the build path via 'without building it', which separates it from deck_build. The dual input mode is named explicitly, so an agent knows both call shapes are in scope.

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?

'without building it' implies pre-build validation as the use case, and 'Call deck_schema for every layout and limit' routes the agent to the right companion tool. It never names deck_build as the alternative nor states an explicit when-not-to-use condition, so guidance is clear but not exhaustive.

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 toolsInspect
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.

Resources