Skip to main content
Glama

list-ui

Search and retrieve UI component data from buouui.com to display matching components and their previews without generating new code.

Instructions

"Use this tool when the user wants to see buouui.com component, or /buou fetch data and previews from buouui.com. This tool returns the JSON data of matching components without generating new code. This tool ONLY returns the text snippet for that UI component. After calling this tool, you need to display the data in the UI, and finally you need to show the website page of the buouui.com."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesFull users message
searchQueryYesSearch query for buouui.com(library for searching UI components) to find a UI component that matches the user's message. Must be a two-four words max or phrase

Implementation Reference

  • src/index.ts:14-14 (registration)
    Registers the ListUiTool instance with the MCP server.
    new ListUiTool().register(server);
  • Zod input schema defining 'message' and 'searchQuery' parameters for the list-ui tool.
    schema = z.object({
      message: z.string().describe("Full users message"),
      searchQuery: z
        .string()
        .describe(
          "Search query for buouui.com(library for searching UI components) to find a UI component that matches the user's message. Must be a two-four words max or phrase"
        ),
    });
  • The execute method that sends a POST request to /api/list with message and searchQuery, returns JSON data or handles errors.
    async execute({ message, searchQuery }: z.infer<typeof this.schema>) {
      try {
        const { data } = await twentyFirstClient.post<FetchUiResponse>(
          "/api/list",
          {
            message,
            searchQuery,
          }
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(data),
            },
          ],
        };
      } catch (error) {
        console.error("Error executing tool:", error);
    
        // 返回更详细的错误信息
        return {
          content: [
            {
              type: "text" as const,
              text: `Error: ${
                error instanceof Error
                  ? error.message
                  : "Failed to generate UI component"
              }. Please try again.`,
            },
          ],
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions the tool returns JSON data without generating code and requires displaying data and a website page afterward, but it doesn't cover permissions, rate limits, error handling, or what 'matching components' entails. The post-call instructions ('display the data in the UI, show the website page') are unclear and not typical tool behavior disclosure.

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

Conciseness2/5

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

The description is poorly structured with run-on sentences and redundancy (e.g., repeating 'buouui.com'). It includes extraneous instructions about post-call actions ('display the data in the UI, show the website page') that don't belong in a tool description. While brief, it's not front-loaded or efficiently written, reducing clarity.

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 tool with two parameters, the description is incomplete. It fails to explain the return format (beyond 'JSON data'), error cases, or how results are matched. The mention of sibling tools without differentiation further reduces completeness, leaving gaps in understanding the tool's role and behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description doesn't add any meaningful parameter semantics beyond what's in the schema (e.g., it doesn't explain how 'message' and 'searchQuery' interact or provide examples). However, it doesn't contradict the schema, so it meets the minimum viable standard.

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

Purpose3/5

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

The description states the tool retrieves UI components from buouui.com and returns JSON data, which clarifies the basic purpose. However, it doesn't clearly distinguish this tool from sibling 'fetch-ui' (both seem to fetch UI data), and the phrasing 'see buouui.com component, or /buou fetch data and previews' is somewhat vague and redundant.

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?

The description provides minimal guidance with 'Use this tool when the user wants to see buouui.com component', but it doesn't explain when to choose this over sibling tools like 'fetch-ui' or 'create-image'. No explicit alternatives, exclusions, or contextual prerequisites are mentioned, leaving usage unclear relative to other tools.

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/buoooou/mcp-ui-gen'

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