Skip to main content
Glama

Get Block Meta Content

get-block-meta-content

Retrieve block metadata content from the FlyonUI MCP server to access UI component information for development workflows.

Instructions

Fetch the content of the block metadata from the FlyonUI MCP server. Use this tool to retrieve the block metadata content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYes

Implementation Reference

  • The handler function that implements the 'get-block-meta-content' tool. It takes an 'endpoint' parameter, appends '?type=mcp' to it, fetches data using apiClient.get, and returns the JSON response formatted as text content. Errors are caught and rethrown with specific messages.
    async ({ endpoint }) => {
        try {
    
            const url = endpoint + "?type=mcp";
            const response = await apiClient.get(url);
    
            if (response.status !== 200) {
                throw new Error(`Failed to fetch block meta content: ${response.status}`);
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(response.data, null, 2),
                    }
                ],
            };
        }
        catch (error) {
            console.error("Error fetching block meta content:", error);
            throw new Error("Failed to fetch block meta content");
        }
    }
  • The input schema for the tool, defining a single required string parameter 'endpoint' using Zod validation.
    inputSchema: { endpoint: z.string() },
  • src/index.ts:142-173 (registration)
    The registration of the 'get-block-meta-content' tool using server.registerTool, specifying the tool name, metadata (title, description), input schema, and the inline handler function.
    server.registerTool(
        "get-block-meta-content",
        {
            title: "Get Block Meta Content",
            description: "Fetch the content of the block metadata from the FlyonUI MCP server. Use this tool to retrieve the block metadata content.",
            inputSchema: { endpoint: z.string() },
        },
        async ({ endpoint }) => {
            try {
    
                const url = endpoint + "?type=mcp";
                const response = await apiClient.get(url);
    
                if (response.status !== 200) {
                    throw new Error(`Failed to fetch block meta content: ${response.status}`);
                }
    
                return {
                    content: [
                        {
                            type: "text",
                            text: JSON.stringify(response.data, null, 2),
                        }
                    ],
                };
            }
            catch (error) {
                console.error("Error fetching block meta content:", error);
                throw new Error("Failed to fetch block meta content");
            }
        }
    );
  • Import of the apiClient helper used in the tool handler for making HTTP GET requests to fetch block meta content.
    import { apiClient } from "./utils/http-client.js";
  • The apiClient object definition, which provides the generic HTTP client methods (including get) used by the tool handler to communicate with the FlyonUI API.
    export const apiClient: HttpClient = {
        get: createMethod("GET"),
        post: createMethod("POST"),
        put: createMethod("PUT"),
        delete: createMethod("DELETE"),
        patch: createMethod("PATCH"),
    };
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. The description only mentions fetching/retrieving content, which implies a read-only operation, but doesn't specify whether this requires authentication, has rate limits, what happens on errors, or the format of returned data. For a tool with zero annotation coverage, this is inadequate behavioral information.

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 appropriately concise with two sentences that directly address the tool's function. While the content is insufficient, the structure is efficient with no wasted words. The first sentence states the action, and the second provides basic usage guidance.

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

Completeness2/5

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

Given the tool has 1 parameter with 0% schema coverage, no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain what differentiates this tool from similar siblings, doesn't document the single parameter, and doesn't describe what the tool returns. For a tool in this context, much more information is needed.

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

Parameters2/5

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

The schema has 1 parameter with 0% description coverage, meaning the 'endpoint' parameter is completely undocumented in the schema. The description provides no information about what 'endpoint' should contain, its format, valid values, or examples. Since schema coverage is 0%, the description should compensate but fails to do so.

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

Purpose2/5

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

The description states 'Fetch the content of the block metadata' which is a tautology of the tool name 'Get Block Meta Content'. It doesn't specify what 'block metadata content' actually contains or what format it returns. While it mentions retrieving from the FlyonUI MCP server, this doesn't meaningfully differentiate it from its sibling tools like 'get-blocks-metadata' or 'get-block-content'.

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

Usage Guidelines2/5

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

The description provides minimal guidance with 'Use this tool to retrieve the block metadata content', which is essentially restating the purpose. It doesn't explain when to use this tool versus alternatives like 'get-blocks-metadata' (plural) or 'get-block-content', nor does it mention any prerequisites, constraints, or specific contexts where this tool is appropriate.

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