Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

Fluxygram turns a small JSON file (.flux.json) into an animated diagram that explains something step by step. Workflow: call get_guide once to learn the format (and get_example for a model to copy), write the diagram JSON, call validate_diagram and fix every issue, then call share_link and give the user the link so they can watch it. Write labels and captions in the user's language.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_guideA

How to write a Fluxygram diagram: the seven diagram types and when to use each, nodes, edges, steps with captions, motion, live status (tracker mode), icons and the storytelling rules. Call it before writing your first diagram.

get_exampleA

Returns a complete example diagram to learn from or adapt. Without a name, lists the available examples (recipes, software architecture, OAuth login, order process, timelines, live order trackers and more).

validate_diagramA

Checks a Fluxygram diagram with the same validator the viewer uses. Returns "valid" with a short summary, or every problem with its path so you can fix it. Always validate before sharing.

share_linkA

Validates the diagram and returns links on fluxygram.app to watch it animated, open it in the editor or present it full screen. The diagram travels inside the link (compressed); nothing is uploaded or stored. Give the view link to the user.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinct phase of the workflow: learning (get_guide, get_example), validating, and sharing. The only mild overlap is between get_guide and get_example, since both are 'learn the format' helpers, but the descriptions clearly separate syntax rules from concrete examples.

Naming Consistency5/5

All four tools use a clean snake_case verb_noun pattern (get_*, share_*, validate_*) with predictable get/get/share/validate semantics.

Tool Count4/5

Four tools is on the lean side, but the server's scope is narrow (write, validate, and share a link-embedded diagram) and each tool earns its place. No filler or duplicate tools.

Completeness4/5

The core lifecycle is covered: learn the format, see an example, validate with the viewer's own validator, and produce a view/editor/present link. Minor gaps exist — no tool to decode or inspect an existing share link, and no export to image/file, but agents can work around both.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues