Skip to main content
Glama

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

get-inspire-instructions

Get step-by-step instructions to create new FlyonUI blocks based on existing examples. Ideal for generating components by inspiration using commands /inspire-flyonui or /iui.

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

  • src/index.ts:45-75 (registration)
    Registration of the 'get-inspire-instructions' tool via server.registerTool() with its title and description.
    // A tool to get instructions for generating FlyonUI blocks using the existing FlyonUI blocks as an inspiration.
    server.registerTool(
        "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");
            }
        }
    );
  • The handler function for 'get-inspire-instructions' that fetches instructions from the /instructions?path=inspire-ui.md endpoint via apiClient.
    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");
        }
    }
  • Schema/metadata definition for the tool: title and description (no input schema defined, as the tool takes no arguments).
    {
        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.",
Behavior3/5

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

No annotations provided, so description carries full burden. It describes the action (get instructions) but does not disclose any side effects, permissions, or format of output. Adequate but not rich.

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?

Two sentences, every word earns its place. Purpose and trigger conditions are front-loaded with no redundancy.

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?

For a simple tool with no output schema, the description gives purpose and usage but does not explain the format or content of the instructions returned. Adequate but could be more 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?

No parameters in schema, and description does not need to add parameter info. Baseline 4 for 0 parameters as per guidelines.

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

Purpose5/5

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

The description clearly states it provides instructions for creating new FlyonUI blocks by inspiration, with specific trigger phrases. It distinguishes from siblings like get-create-instructions.

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?

Explicitly states when to use ('when the user requests to generate a new component by inspirations' and trigger phrases), but does not explicitly exclude alternatives.

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