Skip to main content
Glama

Get Instructions for generating FlyonUI blocks using the existing FlyonUI blocks as an inspiration.

get-inspire-instructions

Generate new UI components by drawing inspiration from existing FlyonUI blocks. This tool provides instructions for creating components when users request inspiration-based generation.

Instructions

Get instructions for working with FlyonUI blocks. This tool provides instructions for creating new FlyonUI blocks by taking the inspiration from existing FlyonUI blocks. Use this tool when the user requests to generate a new component by inspirations. mentions /inspire-flyonui or /iui.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: fetches instructions from `/instructions?path=inspire-ui.md` using the imported apiClient, handles errors, and returns the content as a formatted text response.
    async () => {
        try {
            const url = `/instructions?path=inspire-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:47-75 (registration)
    The registration of the 'get-inspire-instructions' tool using McpServer.registerTool method, including title, description, and inline handler.
        "get-inspire-instructions",
        {
            title: "Get Instructions for generating FlyonUI blocks using the existing FlyonUI blocks as an inspiration.",
            description: "Get instructions for working with FlyonUI blocks. This tool provides instructions for creating new FlyonUI blocks by taking the inspiration from existing FlyonUI blocks. Use this tool when the user requests to generate a new component by inspirations. mentions /inspire-flyonui or /iui.",
        },
        async () => {
            try {
                const url = `/instructions?path=inspire-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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'provides instructions' but doesn't describe what form these instructions take (e.g., text, code snippets), whether it's a read-only operation, if there are any rate limits, or authentication requirements. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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

Conciseness4/5

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

The description is concise and front-loaded, with three sentences that directly address purpose and usage. Each sentence adds value: the first states what the tool does, the second elaborates on inspiration, and the third provides usage triggers. There's no wasted text, though it could be slightly more structured for clarity.

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 the tool's complexity (simple instruction retrieval with no parameters) and lack of annotations and output schema, the description is moderately complete. It covers the purpose and usage well but lacks details on behavioral aspects like output format or operational constraints. This makes it adequate but with clear gaps for an AI agent to fully understand the tool.

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, meaning no parameters are documented in the schema. The description doesn't add parameter details since there are none, which is appropriate. Baseline for 0 parameters is 4, as the description doesn't need to compensate for missing schema information.

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 tool's purpose: 'Get instructions for working with FlyonUI blocks' and specifies it's for 'creating new FlyonUI blocks by taking inspiration from existing FlyonUI blocks.' This provides a specific verb ('get instructions') and resource ('FlyonUI blocks'), though it doesn't explicitly distinguish it from sibling tools like 'get-create-instructions' or 'get-refine-instructions' beyond the inspiration aspect.

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 provides clear usage context: 'Use this tool when the user requests to generate a new component by inspirations. mentions /inspire-flyonui or /iui.' This gives explicit triggers for when to use the tool, but it doesn't specify when not to use it or mention alternatives among the sibling tools, such as when to choose 'get-create-instructions' instead.

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