Skip to main content
Glama

get_all_components

Retrieve all available UI components from the Magic UI design system for use in AI assistants and MCP clients.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that implements the logic for the 'get_all_components' tool. It prefers raw registry data but falls back to parsed components from ComponentParser.getAllComponents().
    async () => {
      // Get the raw content of registry.json
      const rawData = githubService.getRawRegistryData();
      
      // If no data, return processed components as fallback
      if (!rawData || rawData.length === 0) {
        const components = componentParser.getAllComponents();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(components, null, 2),
          }],
        };
      }
      
      // Return the raw content of registry.json
      return {
        content: [{
          type: "text",
          text: JSON.stringify(rawData, null, 2),
        }],
      };
    }
  • src/server.ts:24-50 (registration)
    Registration of the 'get_all_components' tool on the MCP server using server.tool(), with empty input schema and inline handler.
    server.tool(
      "get_all_components",
      {},
      async () => {
        // Get the raw content of registry.json
        const rawData = githubService.getRawRegistryData();
        
        // If no data, return processed components as fallback
        if (!rawData || rawData.length === 0) {
          const components = componentParser.getAllComponents();
          return {
            content: [{
              type: "text",
              text: JSON.stringify(components, null, 2),
            }],
          };
        }
        
        // Return the raw content of registry.json
        return {
          content: [{
            type: "text",
            text: JSON.stringify(rawData, null, 2),
          }],
        };
      }
    );
  • Helper method getAllComponents() in ComponentParser class that returns the list of all parsed components, used as fallback in the tool handler.
    getAllComponents(): Component[] {
      return Array.from(this.components.values());
    }
  • Type definition (schema) for Component objects returned by getAllComponents() and serialized in the tool response.
    export interface Component {
      name: string;
      description: string;
      code: string;
      category: string;
      dependencies?: string[];
      files?: {
        path: string;
        type: string;
        target: string;
      }[];
      title?: string;
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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