Skip to main content
Glama

Elementum Design System MCP

get_component_doc

Retrieves attributes, slots, events, and CSS parts for an Elementum component.

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

Input Schema

NameRequiredDescriptionDefault
tagYesThe custom element tag name, e.g. "el-button" or "el-badge"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Retrieves' does signal a read-only lookup, and the enumerated data categories (attributes, slots, events, CSS parts) tell the agent what a successful call yields. It says nothing about behavior for an unknown or invalid tag, whether results are cached, or the response format.

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, and the returned data categories are listed up front. It is efficient, though terse enough that no structure beyond one clause is present.

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?

With no output schema, the description usefully enumerates the four categories of returned data, which covers the main gap. It still omits error behavior for an unrecognized tag and any indication of output shape or size, leaving a complex docs-lookup tool somewhat under-described.

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?

Only one parameter, and the schema documents it at 100% coverage including example tag names ('el-button', 'el-badge'). The description adds only that the tag refers to an Elementum component, which is marginal beyond the schema baseline of 3.

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 (retrieves) and a specific resource (attributes, slots, events, CSS parts for an Elementum component), so the agent knows exactly what data comes back. It doesn't name a sibling like get_component_maturity or list_components to contrast against, so it falls short of a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_component_maturity or suggest_component. The intended use (look up documentation for a known tag) is only implied by the word 'retrieves'.

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.