Skip to main content
Glama
mastergo-design

MasterGo Magic MCP

Official

mcp__getMeta

Obtain high-level site configuration and page rules from a MasterGo design file. Returns markdown rules and analysis results to guide website construction.

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)
formatNoOutput format for design data. Defaults to json. - json — default; useful when piping output into tools that expect JSON. - yaml — fewer tokens than JSON for typical designs. - tree — experimental compact format. Structural keys (id, name, type) are encoded positionally on each node line, and style values stay deduplicated in a globalVars block. Designs with heavy style reuse see the largest token savings.
layerIdYesLayer ID of the specific component or element to retrieve (format: ?layer_id=<layerId> / file=<fileId> in MasterGo URL)
sourceLayerIdNoSource layer ID from URL parameter source_layer_id. When provided, use this instead of layerId for all queries.
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states that the tool returns 'rules and results,' but does not clarify if the operation is read-only, whether any state changes occur, or any prerequisites (e.g., authentication). This is insufficient for an unannotated tool.

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 a brief paragraph of three sentences, but contains typos ('fileld', 'layerld') and includes an imperative instruction ('you must follow the rules') that could be integrated more concisely. It is not overly long, but clarity is slightly reduced.

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?

The tool has four parameters (including optional format and sourceLayerId) and no output schema. The description does not mention the optional parameters or explain what 'rules and results' means in terms of output structure. For a tool with moderate complexity, the description lacks completeness.

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?

The input schema covers all four parameters with descriptions (100% coverage). The description repeats the need for fileId and layerId but adds no new semantic meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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 specifies that the tool is used when building a complete website or obtaining high-level site configuration, which clearly states its purpose. However, it does not explicitly differentiate this tool from its siblings (e.g., getD2c, getDesignSections), which all retrieve design-related information.

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

Usage Guidelines3/5

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

The description provides usage context ('when user intends to build a complete website') and states that fileId and layerId are required. However, it does not mention when not to use this tool or suggest alternatives among sibling tools, leaving some ambiguity.

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

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