Skip to main content
Glama

explore_components

Fetch and rank animated UI components from UIverse's open-source library. Filter by category, industry, or animation richness to discover community-built components beyond the built-in set.

Instructions

Phase 3.2 — Fetch REAL animated UI components from UIverse.io's open-source library (4,300+ components on GitHub).

This makes the MCP server HYBRID — it goes beyond the built-in 61 components and fetches fresh, community-built components directly from UIverse's GitHub repository (uiverse-io/galaxy).

Returns: actual HTML/CSS code for each component, animation scores, and source URLs.

Components are ranked by animation richness — the most animated components (with @keyframes, transitions, hover effects) are returned first.

Use this to discover new, unique components beyond the built-in library. Combine with select_components for the best of both worlds.

Categories: buttons, cards, loaders, inputs, checkboxes, toggles, radio-buttons, forms, dropdowns, navigation, tooltips, badges, modals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toneNoTone for style-aware filtering. Values: elegant, minimal, bold, playful, modern, warm
industryNoIndustry for style-aware filtering. Filters out incompatible components (e.g., brutalist for luxury). Values: luxury, restaurant, food, corporate, finance, healthcare, education, technology, startup, gaming, creative, ecommerce
categoriesYesComponent categories to explore. Examples: ["buttons", "cards", "loaders", "inputs"]. Supports aliases: "button", "btn", "spinner", etc.
searchQueryNoOptional keyword filter. Examples: "neon", "glow", "gradient", "bounce", "3d"
maxPerCategoryNoMax components to return per category. Default: 5
preferAnimatedNoPrefer components with rich CSS animations. Default: true
Behavior4/5

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

Describes retrieval from external source, return values (HTML/CSS, scores, URLs), and ranking by animation. Implies read-only; no annotations provided, but description is adequate for behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise (~150 words), well-structured, front-loaded with core purpose. Every sentence adds value with no redundancy.

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?

Covers main functionality, return values, and usage context. Lacks details on constraints like rate limits but compensates for missing output schema with description of return values.

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% with detailed parameter descriptions; description adds context on ranking, integration with select_components, and category list, enriching parameter understanding.

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 the tool fetches animated UI components from UIverse's open-source library, distinguishes from built-in components, and lists categories. It goes beyond a tautology with 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use for discovering beyond built-in library and to combine with select_components, providing clear guidance on when to use this tool vs sibling.

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/foduucom/UI-Architect-MCP'

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