Skip to main content
Glama
aerolalit

Pane

by aerolalit
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Manage Templates

template
Destructive

Manage reusable HTML UI templates with versioning, search, and publishing. Create once, use multiple times via pane creation.

Instructions

Manage reusable, versioned UI templates (author once, instance many times via create_pane's template_id). ONE tool with an action enum: create | version | update | search | list | show | get_version | delete | publish | unpublish | search_public | set_icon. Required fields per action are documented on the action parameter. A template is HTML + an event schema (+ optional input/record/template-record schemas); a pane is one use of one version of it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTemplate id or slug. Required for version/update/show/get_version/delete/publish/unpublish/set_icon.
htmlNoHTML template body / source (required for create + version).
nameNoTemplate display name (required for create).
slugNoStable agent-chosen handle (create/update).
tagsNoSearch keywords (create/update).
clearNoset_icon: clear both the emoji and image icon.
limitNosearch_public page size (1..50).
queryNoFree-text search (for search / search_public).
actionYesWhich template operation to run. create: a new named template (needs name+html). version: append a new immutable version to an existing template (id+html). update: patch head metadata (name/slug/description/tags). search/list: find the agent's templates (search takes an optional query). show: full template + version list (id). get_version: one version's content (id+version). delete: remove the template + all versions (id, requires confirm:true). publish/unpublish: public catalog (id). search_public: the public catalog across all agents (optional query). set_icon: set/clear a template's icon (id + one of emoji / icon_attachment_id / clear).
offsetNosearch_public offset.
scopesNoverb:noun permission scopes for publish (e.g. ['read:agent']). Empty array clears them.
confirmNoRequired (true) for the destructive `delete` action.
versionNoVersion number (required for get_version).
icon_emojiNoset_icon: a single-emoji icon.
descriptionNoProse description (create/update).
event_schemaNoEvent schema (create/version). Omit for a view-only template.
input_schemaNoPer-pane input_data JSON Schema (create/version).
record_schemaNoPer-pane record collections schema (create/version).
template_typeNoSource kind. Default html-inline; html-ref treats html as a URL.
icon_attachment_idNoset_icon: a ready template-scoped raster-image attachment id.
template_record_schemaNoTemplate-level (shared) record collections schema (create/version). Set this before using the template_records tool.

Tool Definition Quality

A4.3/5.0
Behavior5/5

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

The description discloses behavioral traits such as the destructive nature of delete (requiring confirm:true) and the concept of versioning, going beyond annotations which only indicate destructiveHint=true.

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?

The description is front-loaded with the core purpose and is structured with a clear action enum. It is slightly verbose but acceptable for the complexity.

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 the tool's complexity (21 params, multiple actions, no output schema), the description explains the conceptual model and defers to action parameter for details. It is fairly complete for an AI agent to understand the tool's domain.

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%, so the schema already documents each parameter. The description adds overarching context and references the action parameter's documentation but does not add per-parameter meaning beyond the schema.

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?

The description clearly states 'Manage reusable, versioned UI templates' and explains the relationship to panes via create_pane's template_id, distinguishing it from pane creation tools. It provides a specific verb and resource.

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?

The description implicitly guides usage by stating templates are authored once and instantiated via create_pane, but does not explicitly state when not to use this tool. It leverages sibling context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aerolalit/paneui'

If you have feedback or need assistance with the MCP directory API, please join our Discord server