Skip to main content
Glama

Get Instructions for refining flyonui blocks/code/component or page.

get-refine-instructions

Provides instructions for refining existing FlyonUI UI components when users request to modify or improve blocks, supporting frameworks like React, Next.js, Vue, and Svelte.

Instructions

Get instructions for refining FlyonUI blocks. This tool provides instructions for refining existing FlyonUI blocks. Use this tool when the user requests to refine an existing component. mentions /refine-flyonui or /rui.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:78-107 (registration)
    Registers the 'get-refine-instructions' tool with server.registerTool, including title, description, and the inline handler function.
    server.registerTool(
        "get-refine-instructions",
        {
            title: "Get Instructions for refining flyonui blocks/code/component or page.",
            description: "Get instructions for refining FlyonUI blocks. This tool provides instructions for refining existing FlyonUI blocks. Use this tool when the user requests to refine an existing component. mentions /refine-flyonui or /rui.",
        },
        async () => {
            try {
                const url = `/instructions?path=refine-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");
            }
        }
    );
  • Inline handler function for the tool that performs an HTTP GET request to `/instructions?path=refine-ui.md` using apiClient, returns the response data as formatted JSON text content, and handles errors appropriately.
    async () => {
        try {
            const url = `/instructions?path=refine-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 describes the tool as a 'get' operation for instructions, implying it's read-only and non-destructive, but doesn't specify any behavioral traits such as response format, potential errors, or any constraints. This leaves gaps in understanding how the tool behaves 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, stating the purpose in the first sentence and usage guidelines in the second. It avoids unnecessary details, but the repetition of 'refining' in the first two sentences slightly reduces efficiency. Overall, it's well-structured with minimal waste.

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 has 0 parameters, no annotations, and no output schema, the description provides adequate purpose and usage context. However, it lacks details on what the instructions entail (e.g., format, content) or any behavioral aspects, making it incomplete for fully understanding the tool's operation in a complex environment.

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 semantics, which is appropriate here. A baseline score of 4 is given because the schema fully covers the lack of parameters, and the description doesn't need to compensate.

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 refining existing FlyonUI blocks', which clarifies the verb (get instructions) and resource (FlyonUI blocks). However, it doesn't differentiate from sibling tools like 'get-create-instructions' or 'get-inspire-instructions' beyond mentioning 'refining' versus 'creating' or 'inspiring', leaving some ambiguity about the specific scope of refinement 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?

The description explicitly states 'Use this tool when the user requests to refine an existing component' and includes trigger phrases like 'mentions /refine-flyonui or /rui', providing clear context for when to use it. However, it doesn't mention when not to use it or explicitly compare to alternatives like 'get-create-instructions', 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