Skip to main content
Glama

Elementum Design System MCP

scaffold_component

Scaffolds standard boilerplate JavaScript code for a new Elementum Web Component adhering to design system standards.

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": "scaffold_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesComponent tag, e.g. "el-card"
nameNoComponent class name, e.g. "ElCard"
attributesNoObserved attributes, e.g. ["variant", "disabled"]
descriptionNoComponent description
formAssociatedNoWhether the component associates with forms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it leaves the most consequential question unanswered: whether "scaffolds" writes files to disk or merely returns a code string, and if it writes, where files land and whether existing files are overwritten. There is no disclosure of side effects, idempotency, or permissions, which matters for a code-generation tool with zero annotation coverage.

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 well-formed sentence with the verb front-loaded and zero filler; nothing is redundant. It is lean to the point of being slightly under-specified, but the structure itself is clean.

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 five-parameter generator with no output schema and no annotations, the description is minimal. It never describes what comes back (generated code text, file path, or created files) nor the side effects of generation, which the agent needs in order to chain this into a workflow.

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%, so every one of the five parameters (tag, name, attributes, description, formAssociated) is already documented in the schema. The description adds no meaning beyond that, which is the baseline 3 when the schema does the heavy lifting.

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 ("Scaffolds") and a specific artifact ("standard boilerplate JavaScript code for a new Elementum Web Component"), so the agent knows exactly what it produces. It does not, however, contrast itself with sibling tools like generate_snippet or suggest_component, leaving differentiation to inference.

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 phrase "for a new Elementum Web Component" implies the usage context (bootstrapping a brand-new component), which is better than nothing. But there is no explicit when-to-use versus when-not guidance, no mention of prerequisites or the alternative generation/validation tools, and no note on whether this is appropriate for existing components.

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.