Skip to main content
Glama

Elementum Design System MCP

generate_snippet

Generates valid Elementum Web Component HTML markup matching Figma variants.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tag": "<tag>"
    },
    "name": "generate_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesComponent tag, e.g. "el-button"
sizeNoSize variant, e.g. "sm", "md", "lg"
labelNoContent text for the default slot
variantNoVisual variant, e.g. "primary", "secondary", "danger"
disabledNoWhether the element is disabled

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It adds the useful claim that generated markup is valid and Figma-consistent, but says nothing about whether markup is returned or written to disk, whether generation is side-effect free, or any auth/precondition requirements. For a generation tool with zero annotation coverage this is a notable gap.

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?

A single front-loaded sentence with no filler; the core action and output type come first. It is efficient, though the brevity contributes to the missing-guidance gaps noted elsewhere.

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?

The description does specify the output type (HTML markup), which is the main thing needed since no output schema exists, and the schema fully covers inputs. However, for a five-parameter generation tool with no annotations, the lack of any usage routing or side-effect disclosure leaves it only minimally adequate.

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 coverage is 100%, so each of the five parameters is already documented in the schema, and the baseline of 3 applies. The phrase "matching Figma variants" loosely ties to the variant/size fields but adds no syntax, allowed values, or defaults beyond what the schema states.

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?

States a specific verb ("Generates") and a concrete resource ("valid Elementum Web Component HTML markup") with the added qualifier that output matches Figma variants. It does not differentiate from siblings like scaffold_component or suggest_component, which could plausibly overlap, so an agent cannot fully rule out alternatives from the text alone.

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?

No when-to-use or when-not-to-use guidance is given; nothing tells the agent to prefer this over scaffold_component or get_component_doc. The only implied usage is 'you have a component tag and want markup,' which the agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.