A2UI Atomic Catalog

emit_deployment

Read-onlyIdempotent

🎓 GRADUATE a tested surface into a dedicated, DEPLOYER-ONLY standing app in YOUR OWN Google Apps Script account. Returns a deterministic recipe (config files + clasp ops + least-privilege scopes derived from the atoms + verify) — you run it with your own clasp; nothing runs on our side, we hold no creds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payload": "<payload>"
    },
    "name": "emit_deployment"
  }
}

Input Schema

Name	Required	Description	Default
`payload`	Yes	The tested A2UI payload to bake into the standing app as its home surface: {title, theme, blocks:[...]}.
`app_name`	No	Name for the Apps Script project and its folder. Defaults to the payload title, else "A2UI App".

Output Schema

Name	Required	Description
`ops`	Yes	Ordered shell steps to build and deploy.
`note`	Yes	What the recipe does.
`files`	Yes	File name to file content for the Apps Script project (HomeSurface.gs, appsscript.json).
`inputs`	Yes	Resolved inputs.
`verify`	Yes	How to check the deployed app.
`renderer_source`	No	Where to fetch the open renderer.
`required_catalogs`	Yes	Catalog URIs the payload needs (base catalog first).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: nothing runs server-side, no credentials are held, and the output is a recipe the caller executes with their own clasp. This is a real value-add and not a contradiction.

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?

Two dense sentences with the core action front-loaded and the operational caveat (nothing runs on our side) placed second. Some jargon and capitalized emphasis, but nothing is wasted.

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?

Given an output schema, nested payload object, and annotations covering the safety profile, the description carries enough: what it produces, what it does not do, and who executes the result. The main gap is routing guidance relative to sibling emit tools.

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%, so the schema already documents payload, blocks, title, theme, and app_name defaults. The description only loosely ties 'atoms' to the scopes it derives and adds no format or constraint detail beyond what the schema provides.

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 and resource: graduate a tested surface into a deployer-only standing Apps Script app, returning a deterministic recipe of config files, clasp ops, scopes, and verify steps. The purpose is clear from the description alone, though it does not name or distinguish itself from sibling emit tools such as emit_runbook_surface or emit_training_runbook.

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

Usage Guidelines3/5

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

Implies usage through the word 'tested' and 'GRADUATE' — use it after a surface is validated — but never states when to use this instead of the other emit_* siblings, nor any exclusions. Usage is inferable but not explicit.

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.