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.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_sitesB

Search award-winning websites on Awwwards. Returns site cards with inline screenshots, live URLs, awards and tags.

get_site_detailsA

Get the design DNA of one Awwwards site: color palette, technologies, design elements, awards, description and inline screenshot.

compare_sitesA

Compare the design DNA of 2–3 Awwwards sites: titles, live URLs, palettes, technologies, elements, awards and jury scores. Text only; missing details are fetched and cached.

create_design_briefC

Synthesize a cited design direction from 2–5 Awwwards references

get_index_statusA

Read offline index status: cached site count, progress, last successful finish and error, lock state and freshness. No live requests.

get_site_elementsA

Get the design-element highlights of one Awwwards site: component-level visuals (3D models, video content, mobile layouts, microcopy) with poster images inline and video URLs.

search_elementsA

Search Awwwards' curated element gallery — award-grade UI components (footers, menus, loaders, transitions, micro-interactions…). Usage: pass query text and at most one of category/stack; every result links back to its source element page and parent project.

get_elementA

Get one Awwwards element in full: title, author, built-with stack, media URLs, related elements and the parent award-winning project. Use search_elements first for ids.

list_categoriesA

List the filter taxonomy available on Awwwards: color hexes and tag/technology slugs usable with search_sites.

capture_live_siteA

Take a fresh full-page screenshot of a live website URL using a headless browser. Requires the optional playwright dependency.

analyze_page_structureA

Extract a page's section band map (tag, label, background color, offset, height per band) via a headless browser. Works on live URLs and file:// paths — use it to compare a reference site's structure against your local build.

record_site_motionA

Record a short motion-through video of a live website — preloader, scroll-triggered and hover/cursor animations — and return an inline filmstrip JPEG plus the .webm path. Requires the optional playwright and ffmpeg-static dependencies. Also writes a Motion Evidence Sheet (keyframes with census-stamped captions, diff masks, cursor-trail overlay, timeline strip) beside the filmstrip.

get_motion_dnaA

Get the Motion DNA of a website: animation stack, ScrollTrigger/pin/scrub counts, easing vocabulary and duration distribution. Serves the corpus first; live-captures unseen URLs (headless browser required).

analyze_scroll_map

Per-element motion census of a live page: what animates, its CSS properties, duration, delay, easing, and what triggered it (GSAP ScrollTrigger, native CSS scroll()/view() timelines, data attributes, SMIL/SVG). Includes svgStrokes list for stroke draw-in effects. Runs on any URL you give it (builds, references) — does not fetch awwwards.com. Run twice (with reducedMotion) to audit prefers-reduced-motion degradation. Optional scrubProbe drives the page and returns real progress curves per scrubbed trigger. Every payload also carries a choreography block: stagger hints (hint selector/value/source, groups) distilled from GSAP tween vars and stepped delays across sibling animations.

analyze_hover_censusA

:hover interaction census of a live page: counts hover rules, samples up to 20 interactive elements, and reports which CSS properties change on hover with transition duration and easing. Use it to reproduce micro-interactions and verify interaction-state coverage. Runs on any URL — does not fetch awwwards.com.

analyze_bundle

Bundle forensics for a live page: fetch it once, download its script chunks (script tags, inline scripts, and modulepreload/preload-as-script hints; bounded: ≤40 chunks, 10MB, 1 request/second), save them locally, optionally de-obfuscate with webcrack if installed, and grep keywords across the code. Returns chunk paths + match lines so an agent can read the actual animation mechanism instead of guessing. Runs on URLs you are authorized to analyze — does not fetch awwwards.com.

verify_buildA

Compare a built site against a reference (an Awwwards winner, a client's old site, any URL): band-structure match + motion fingerprint similarity, with a pass/warn/fail verdict and evidence lines. Closes the design loop: build → verify → fix → re-verify.

capture_componentB

Serialize a page component (structure, computed-style tokens, animations) into a portable pack for rebuild tooling. Runs on any URL — does not fetch awwwards.com.

capture_pose_3dA

Capture a page's WebGL/canvas 3D pose grid: samples the largest canvas (toDataURL, viewport-screenshot fallback) at up to 10 scroll steps with per-step scroll ratios, for reconstructing scroll-driven 3D camera paths. Runs on any URL — does not fetch awwwards.com. Requires the optional playwright dependency.

build_pose_stubA

Render a captured pose grid (pose-grid-v1 from capture_pose_3d) as a standalone scroll-scrubbed three.js stub page: frames preloaded inline, camera path interpolated between snapshot scroll ratios, prefers-reduced-motion static fallback, optional census-derived st/pin/ease suggestions. Pure build — no page fetches, no awwwards.com access.

analyze_stack

Fingerprint a page's framework (Next.js/Astro/Nuxt/Remix/SvelteKit/WordPress/Webflow/Framer), CSS framework (Tailwind/Bootstrap), and marker libs from fetched HTML — runs on any URL, one polite request, no browser

build_gsap_stub

Generate a runnable GSAP+ScrollTrigger timeline stub from captured motion evidence (scroll census anims + optional pose grid camera anchors) — pure build from provided JSON, no page fetches

search_motionA

Search captured Motion DNA records: find sites that pin sections, scrub scroll-driven animation, or run a given animation library. Corpus only — live-capture happens via get_motion_dna.

new_winnersA

Poll today's new Awwwards winners as a delta against the previous poll: new-entrant cards since the last call (first call seeds the baseline and reports no delta). Poll daily for a winners feed; pairs with watch_site for structured monitoring.

watch_siteA

Longitudinal watchlist over Awwwards listings: track a studio (e.g. 'ToyFight'), a tag/technology slug (e.g. 'webgl'), or a site URL-slug for changes and new entries. add/list/remove; the delta is reported by watch_site list after new_winners or search_sites refreshes the listing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 22 tools

Disambiguation3/5

Search tools (search_sites, search_elements, search_motion) target distinct resources and are clear, but the live-capture/analysis cluster is crowded: get_motion_dna, analyze_scroll_map, record_site_motion, capture_live_site, and capture_component all describe extracting motion/structure from a page and their boundaries blur (scrollTrigger counts appear in both get_motion_dna and analyze_scroll_map). new_winners and watch_site also overlap in tracking newly-listed entries, risking misselection.

Naming Consistency4/5

Names are consistently snake_case and overwhelmingly follow a verb_noun pattern (capture_live_site, analyze_scroll_map, search_elements, get_site_details, verify_build). Minor deviations exist, e.g. new_winners is a bare noun and watch_site/compare_sites are a bit terse, but nothing breaks the pattern.

Tool Count3/5

22 tools is on the heavy side for the surface. While the domain (discovery, detail, live capture, motion analysis, build synthesis) is broad, several capture/analysis tools duplicate overlapping capability, so not every tool clearly earns its place.

Completeness4/5

Coverage is strong: search, site/element details, comparison, live capture, motion/scroll/hover analysis, pose capture and stub building, plus brief synthesis and verification form a fairly complete pipeline. Minor gaps like no explicit update/edit for watch entries beyond add/list/remove, but core workflows have no dead ends.

Maintenance

ActivityActive
ResponsivenessWithin a week