Skip to main content
Glama
mastergo-design

MasterGo Magic MCP

Official

mcp__getMeta

Retrieve high-level site configuration and design rules by providing a MasterGo design file ID and layer ID. Use the returned markdown rules and results to analyze and build websites.

Instructions

Use this tool when the user intends to build a complete website or needs to obtain high-level site configuration information. You must provide a fileld and layerld to identify the specific design element. This tool returns the rules and results of the site and page. The rules is a markdown file, you must follow the rules and use the results to analyze the site and page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdYesMasterGo design file ID (format: file/<fileId> in MasterGo URL)
layerIdYesLayer ID of the specific component or element to retrieve (format: ?layer_id=<layerId> / file=<fileId> in MasterGo URL)

Implementation Reference

  • The execute method implements the core logic of the mcp__getMeta tool. It fetches metadata using httpUtilInstance.getMeta(fileId, layerId), includes site rules, and returns structured content or error.
    async execute({ fileId, layerId }: z.infer<typeof this.schema>) {
      try {
        const result = await httpUtilInstance.getMeta(fileId, layerId);
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                result,
                rules,
              }),
            },
          ],
        };
      } catch (error: any) {
        const errorMessage = error.response?.data ?? error?.message;
        return {
          isError: true,
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(errorMessage),
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters: fileId (MasterGo design file ID) and layerId (layer ID). Used for input validation in the MCP tool.
    schema = z.object({
      fileId: z
        .string()
        .describe(
          "MasterGo design file ID (format: file/<fileId> in MasterGo URL)"
        ),
      layerId: z
        .string()
        .describe(
          "Layer ID of the specific component or element to retrieve (format: ?layer_id=<layerId> / file=<fileId> in MasterGo URL)"
        ),
    });
  • src/index.ts:37-37 (registration)
    Registers the GetMetaTool instance with the MCP server using its register method, which internally calls server.tool with name, description, schema, and execute handler.
    new GetMetaTool().register(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool 'returns the rules and results' and that 'rules is a markdown file', but doesn't specify whether this is a read-only operation, what permissions might be required, rate limits, error conditions, or how the results should be interpreted beyond 'use the results to analyze'. This leaves significant behavioral gaps for a tool that appears to retrieve configuration data.

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 reasonably concise at 4 sentences, but could be more front-loaded. The first sentence establishes usage context, but the core purpose ('returns the rules and results') comes later. The final sentence about following rules and analyzing feels somewhat redundant with earlier content.

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 tool with 2 parameters (100% schema coverage) but no annotations or output schema, the description provides basic purpose and usage context. However, it doesn't adequately explain what 'rules and results' actually contain, how they're structured, or what 'analyze the site and page' means in practical terms. The lack of output schema means the description should ideally provide more detail about return values.

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

Parameters3/5

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

Schema description coverage is 100%, with both parameters (fileId and layerId) well-documented in the schema. The description adds that these parameters 'identify the specific design element', which provides some additional context about their purpose, but doesn't offer significant semantic value beyond what the schema already provides about MasterGo design files and layer IDs.

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 is used to 'obtain high-level site configuration information' and 'returns the rules and results of the site and page', which provides a general purpose. However, it doesn't clearly differentiate from sibling tools like mcp__getComponentGenerator or mcp__getComponentLink, nor does it specify the exact resource being retrieved beyond 'site and page' information.

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 intends to build a complete website or needs to obtain high-level site configuration information', providing clear context for when to use it. However, it doesn't mention when NOT to use it or provide specific alternatives among the sibling tools listed.

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

Related 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/mastergo-design/mastergo-magic-mcp'

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