Skip to main content
Glama

aui_generate_ui

Transform raw JSON arrays, CSV, SQL query rows, or a public webpage URL into an interactive, XSS-isolated AUI iframe (embed_url) in <50ms. Supports 4 specialized engines: 'dt' (Signature 2-Line DataTables with avatars, foldable child drawers, facet pills & CSV export), 'cg' (Apache ECharts bar/line/pie/radar/scatter), 'tl' (Omni-Time V3 60fps Spatial Timeline + 32% Synced Side Fold List), and 'dp' (DayPilot 2D Resource x Time Scheduler Tape). Works immediately with zero API key (deterministic sandbox) or with an AUI trial/production key.

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": "aui_generate_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional public URL to scrape and visualize if data is omitted.
dataNoJSON array, object, or CSV string of records/events to visualize.
themeNoColor theme for the embedded widget.dark
promptNoNatural-language visualization goal or title instruction.
actionsNoOptional cross-domain postMessage action buttons (e.g. [{action_name:'openRecord', id_column:'id', label:'Inspect'}]).
ui_typeNoTarget AUI engine ('auto' inspects payload shape automatically).auto
chart_typeNoPreferred chart subtype when ui_type is 'cg'.auto
aui_api_keyNoOptional AUI trial-... or paid key (can also be sent via Authorization: Bearer header).
gemini_api_keyNoOptional BYOK Gemini key when using an unbacked trial key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does it well: XSS-isolated iframe output, sub-50ms latency, zero-key deterministic sandbox mode, and the BYOK Gemini path. It stops short of error/rate-limit behavior and exact return shape beyond the embed_url mention.

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?

Dense but front-loaded: the transformation and output artifact come first, then engine breakdown, then auth. Two long sentences; no filler, though the engine catalogue is packed tightly enough to be slightly hard to scan.

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?

For a 9-parameter tool with no annotations and no output schema, the description covers engines, data sources, auth modes, and the returned embed_url. Minor gaps remain around failure modes and what the iframe payload actually contains.

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 100%, so baseline is 3, but the description adds real meaning by unpacking the ui_type enum values (what 'dt', 'cg', 'tl', 'dp' actually render) and the auto-inspection behavior, beyond the schema's one-line enum labels.

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 (transform) and resource (raw JSON/CSV/SQL rows/URL into an interactive AUI iframe, embed_url), and names the exact output artifact. The four engine codes (dt, cg, tl, dp) are each described so an agent can distinguish them without opening the 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?

Explains key contexts: works with zero API key via deterministic sandbox, or with a trial/production key, and that 'auto' inspects payload shape. It does not explicitly route against the sibling tools (claim trial, share widget, verify key), so when-not guidance is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources