vizcharter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vizcharter_createA | Render a VizCharter diagram from a spec and export it. Returns a PNG preview (look at it and iterate!), written file paths, embed snippets, and lint findings. Spec family 'architecture': { family:'architecture', title?, subtitle?, theme? (vizcharter-light|vizcharter-dark|aws), direction? ('AUTO' default — lays out both ways and keeps the tighter canvas | 'DOWN' | 'RIGHT'), nodes:[{id, icon? (registry id, see vizcharter_icons), label, sublabel?, parent? (container id), pin?:{x,y}}], containers:[{id, type:'region'|'account'|'vpc'|'subnet'|'az'|'layer'|'group', label, parent?}], edges:[{from, to, kind?:'sync'|'async'|'config'|'data', label?}], callouts?:[{n, at}], legend?:boolean }. Layer containers auto-rotate pastel tints; edge kinds get distinct styling and an auto legend. Spec family 'chart': { family:'chart', type:'bar'|'bar-stacked'|'bar-grouped'|'line'|'area'|'donut'|'pie'|'rose'|'venn'|'kpi', title?, theme?, width?, height?, categories?+series? (axis types), slices? (donut/pie/rose), sets?+overlaps? (venn, 2-3 sets), tiles? (kpi: {label, value, delta?, sublabel?}), options?: { showValues?, showLegend?, donutLabel? } } — same design tokens as diagrams. Spec family 'canvas' (infographics/posters): { family:'canvas', theme?, page?:{width,height,background?}, template?:{name, slots} (see vizcharter_templates; auto-sizes the page), layers?:[ {kind:'text', x,y,width?,text,style?,align?} | {kind:'shape', shape:'rect'|'circle'|'line', ...} | {kind:'icon', icon,x,y,size} | {kind:'chart', x,y,spec} | {kind:'arch', x,y,scale?,spec} | {kind:'svg', x,y,content} (raw-SVG escape hatch) ] — embed full chart/architecture specs into posters. ALL families accept an optional |
| vizcharter_updateA | Update an existing diagram from its .vizc.json source. Applies an RFC 7386 JSON merge patch (objects merge recursively, null deletes a key, arrays replace wholesale) or a full replacement, then re-renders and re-exports to the same location. Returns the new preview and lint findings. |
| vizcharter_exportA | Re-export an existing diagram (.vizc.json source) to additional formats or scales without changing it. Note: new formats are added to the diagram's directory alongside existing exports. |
| vizcharter_iconsA | Fuzzy-search the bundled official cloud icon packs — AWS, GCP, and Azure (1100+ icons). Returns icon registry ids (aws.lambda, gcp.bigquery, azure.kubernetes-services, …) to use as node |
| vizcharter_themesA | List built-in themes, or validate custom theme overrides (pass |
| vizcharter_templatesA | List the canvas poster templates with their slot schemas. Use with spec family 'canvas': { family:'canvas', template: { name, slots } } — the template computes layout and page size; add |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct part of the workflow: create for new diagrams, update for editing existing sources, export for additional formats, and icons/themes/templates for asset lookup. The only mild overlap is that create and update both render and export, but their inputs and intent are clearly separated.
All tools share the lowercase snake_case 'vizcharter_' prefix and are easy to group. The action tools use verbs while the lookup tools use bare nouns, which is a minor grammatical inconsistency but still predictable and readable.
Six tools is a well-scoped size for a diagramming server: three lifecycle operations plus three supporting catalogs. No tool feels redundant or extraneous.
The core create/update/export lifecycle is covered, and icons, themes, and templates support the main spec families well. There is no delete or discovery tool for existing diagrams, but since create and update return paths and export consumes a known source, this is a workable minor gap.