Skip to main content
Glama
mastergo-design

MasterGo Magic MCP

Official
by mastergo-design
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

mcp__getDsl

Retrieve full DSL data from MasterGo designs by fileId and layerId or short link. Use as fallback when getDesignSections fails; returns raw data for parsing and code generation.

Instructions

[FALLBACK] Use only when mcp__getDesignSections is unavailable or returns an error. This returns the FULL DSL in one response — may be large and exceed context limits for complex designs. Prefer mcp__getDesignSections as the primary tool for all designs. You can provide either:

  1. fileId and layerId directly, or

  2. a short link (like https://{domain}/goto/LhGgBAK) This tool returns the raw DSL data that you can then parse and analyze. Use the optional 'format' parameter (json/yaml/tree, defaults to json) to control the serialization. This tool also returns the rules you must follow when generating code. The DSL data can also be used to transform and generate code for different frameworks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdNoMasterGo design file ID (format: file/<fileId> in MasterGo URL). Required if shortLink is not provided.
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.
layerIdNoLayer ID of the specific component or element to retrieve (format: ?layer_id=<layerId> / file=<fileId> in MasterGo URL). Required if shortLink is not provided.
shortLinkNoShort link (like https://{domain}/goto/LhGgBAK).
sourceLayerIdNoSource layer ID from URL parameter source_layer_id. When provided, use this instead of layerId for all queries.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided, but the description warns that the response may be large and exceed context limits, discloses it returns raw DSL data and rules for code generation, and explains the format parameter behavior. Auth or rate limits are not mentioned, but the key behavioral trait of size is covered.

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 well-structured with clear sections and front-loading of purpose and fallback role. It is slightly verbose but each sentence adds value. Could be more concise, but overall it is effective.

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

Completeness5/5

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

Given the tool has 5 parameters, no output schema, and no annotations, the description covers all necessary aspects: purpose, usage guidelines, parameter explanation, output characteristics, and behavioral warnings. It is fully sufficient for an agent to select and invoke the tool correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds context beyond the schema by explaining the fallback scenario, clarifying how shortLink relates to fileId/layerId, and describing the outcome of each format option. This extra guidance justifies a score of 4.

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 the tool returns the full DSL in one response, functions as a fallback for mcp__getDesignSections, and distinguishes itself by warning of large output. Purpose is specific and unambiguous.

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

Usage Guidelines5/5

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

Explicitly says 'Use only when mcp__getDesignSections is unavailable or returns an error' and 'Prefer mcp__getDesignSections as the primary tool,' providing clear when-to-use and when-not-to-use guidance. Also explains two ways to provide input (fileId+layerId or shortLink).

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