Skip to main content
Glama
iannuttall

Flux UI MCP Server

by iannuttall

list_flux_components

Retrieve all available Flux UI components to access documentation and examples for the design system.

Instructions

Get a list of all available Flux UI components

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:101-109 (registration)
    Registration of the list_flux_components tool, including its description and empty input schema (no parameters required).
    {
      name: "list_flux_components",
      description: "Get a list of all available Flux UI components",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • src/index.ts:157-158 (registration)
    Dispatch case in CallToolRequestSchema handler that routes to the tool's implementation method.
    case "list_flux_components":
      return await this.handleListComponents();
  • Core implementation of the list_flux_components tool. Fetches the Flux UI components page, scrapes anchor links starting with /components/, extracts component names from URLs, caches the list, and returns an array of {name, url} objects.
    private async handleListComponents() {
      try {
        if (!this.componentsListCache) {
          // Fetch the main components page or sidebar structure
          // This needs inspection of fluxui.dev to find the component list reliably
          // Let's assume we fetch the base URL and look for links starting with /components/
          const response = await this.axiosInstance.get(`${this.FLUX_DOCS_URL}/components`);
          const $ = cheerio.load(response.data);
    
          const components: ComponentInfo[] = [];
          const componentUrls = new Set<string>(); // Avoid duplicates
    
          // Look for links within the navigation or main content area
          // Adjust selector based on actual site structure
          $('a[href^="/components/"]').each((_, element) => {
            const link = $(element);
            const url = link.attr("href");
    
            if (url && url !== "/components" && !componentUrls.has(url)) {
               // Basic check to avoid the parent page
               // Extract name from URL
              const parts = url.split("/").filter(part => part); // filter removes empty strings
              const name = parts[parts.length - 1];
    
              if (name && !name.includes('#')) { // Basic check for valid component name
                componentUrls.add(url);
                components.push({
                  name,
                  description: "", // Will be populated when fetching details
                  url: `${this.FLUX_DOCS_URL}${url}`,
                });
              }
            }
          });
    
          // Sort components alphabetically by name
          components.sort((a, b) => a.name.localeCompare(b.name));
    
          this.componentsListCache = components;
        }
    
        return this.createSuccessResponse(
            this.componentsListCache.map(c => ({ name: c.name, url: c.url })) // Return only name and URL for list
          );
    
      } catch (error) {
         this.handleAxiosError(error, "Failed to fetch Flux UI components list");
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves a list but doesn't disclose behavioral traits such as whether it's read-only, if there are rate limits, what the return format looks like (e.g., pagination, structure), or any authentication requirements. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It lacks information on behavioral aspects (e.g., return format, safety) and usage context, which are necessary for the agent to effectively invoke it, especially with sibling tools available.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and since there are none, it doesn't need to compensate for any gaps, earning a baseline score above 3 for this scenario.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('list of all available Flux UI components'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_flux_components' (which might filter components) or 'get_flux_component_details' (which provides detailed info on a specific component), missing full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention contexts like needing a comprehensive list versus filtered results, or prerequisites for usage, leaving the agent to infer based on sibling tool names alone.

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/iannuttall/flux-ui-mcp'

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