Skip to main content
Glama

Get Instructions for FlyonUI.

get-create-instructions

Provides step-by-step instructions for creating new FlyonUI UI components by leveraging existing blocks within your IDE, enabling developers to generate custom components for React, Next.js, Vue, or Svelte projects.

Instructions

Get instructions for creating FlyonUI blocks using existing blocks. This tool provides instructions for creating new FlyonUI blocks using existing blocks. Use this tool when the user requests to generate a new component. mentions /create-flyonui or /cui. Strictly follow the steps one by one to ensure successful code generation.Retrieves Instructions for IDE agent to follow for creating/generating/updating FlyonUI blocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'get-create-instructions' tool. Fetches instructions from '/instructions?path=create-ui.md' using apiClient and returns the data as text content.
    async () => {
        try {
            const url = `/instructions?path=create-ui.md`;
            const response = await apiClient.get(url);
    
            if (response.status !== 200) {
                throw new Error(`HTTP error! status: ${response.status}`);
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(response.data, null, 2),
                    }
                ],
            };
        }
        catch (error) {
            console.error("Error fetching block metadata:", error);
            throw new Error("Failed to fetch block metadata");
        }
    }
  • src/index.ts:14-43 (registration)
    Registers the 'get-create-instructions' tool with MCP server, including title, description, and inline handler.
    server.registerTool(
        "get-create-instructions",
        {
            title: "Get Instructions for FlyonUI.",
            description: "Get instructions for creating FlyonUI blocks using existing blocks. This tool provides instructions for creating new FlyonUI blocks using existing blocks. Use this tool when the user requests to generate a new component. mentions /create-flyonui or /cui. Strictly follow the steps one by one to ensure successful code generation.Retrieves Instructions for IDE agent to follow for creating/generating/updating FlyonUI blocks.",
        },
        async () => {
            try {
                const url = `/instructions?path=create-ui.md`;
                const response = await apiClient.get(url);
    
                if (response.status !== 200) {
                    throw new Error(`HTTP error! status: ${response.status}`);
                }
    
                return {
                    content: [
                        {
                            type: "text",
                            text: JSON.stringify(response.data, null, 2),
                        }
                    ],
                };
            }
            catch (error) {
                console.error("Error fetching block metadata:", error);
                throw new Error("Failed to fetch block metadata");
            }
        }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieving instructions and following steps, but lacks details on permissions, rate limits, error handling, or what the instructions entail (e.g., format, length). This leaves gaps in understanding how the tool behaves beyond basic retrieval.

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

Conciseness3/5

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

The description is moderately concise but repetitive, e.g., 'Get instructions for creating FlyonUI blocks using existing blocks. This tool provides instructions for creating new FlyonUI blocks using existing blocks.' It could be more streamlined. However, it front-loads the purpose and includes usage guidelines, making it somewhat structured.

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

Completeness3/5

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

Given no annotations, 0 parameters, and no output schema, the description is adequate for a simple retrieval tool but lacks depth. It covers purpose and usage but misses behavioral details like what the instructions contain or how they're formatted. For a tool with no structured data, it should provide more context to be fully complete.

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 doesn't add parameter details, which is appropriate here. It does imply context about user requests and commands, but since parameters aren't required, this doesn't detract from clarity.

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 'provides instructions for creating new FlyonUI blocks using existing blocks,' which clarifies its purpose as retrieving instructional content. However, it's somewhat vague about what exactly 'instructions' entail and doesn't clearly differentiate from sibling tools like 'get-inspire-instructions' or 'get-refine-instructions,' leaving ambiguity in scope.

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

Usage Guidelines4/5

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

The description specifies to 'Use this tool when the user requests to generate a new component, mentions /create-flyonui or /cui,' providing clear contextual triggers. It also instructs to 'Strictly follow the steps one by one,' adding procedural guidance. However, it doesn't explicitly state when not to use it or compare alternatives among siblings, missing full differentiation.

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/themeselection/flyonui-mcp'

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