Skip to main content
Glama

Elementum Design System MCP

suggest_component

Recommends Elementum Web Components that best match a UI requirement or natural-language query.

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": {
      "query": "<query>"
    },
    "name": "suggest_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default 5)
queryYesUI requirement, e.g. "date picker", "code diff", "command palette"

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?

No annotations are supplied, so the description carries the full behavioral burden. It does not state that the operation is read-only, whether results are ranked or scored, or how matching works (keyword vs semantic), leaving an agent to infer safety and result quality.

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 no filler, and the core purpose is front-loaded. It could only be improved by trading a few words for one concrete usage cue.

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 simple two-parameter recommendation tool with no output schema, this is close to adequate, but the absence of an output schema means the description should explain what a recommendation contains (component name, rationale, ranking) and whether results are ordered by relevance.

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% and both parameters are documented in the schema, so the baseline is 3. The description adds the useful nuance that the query accepts natural-language UI requirements, but contributes nothing beyond the schema for the limit parameter.

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 names a specific verb ("Recommends") and a specific resource ("Elementum Web Components") plus the matching criterion (a UI requirement or natural-language query). It is distinct from siblings like list_components or get_component_doc, but it never explicitly contrasts itself with them.

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?

Usage is implied by the phrase "best match a UI requirement or natural-language query," which tells an agent this is for discovery-from-a-need rather than browsing or fetching docs. There is no explicit when-not guidance and no named alternative such as list_components for enumerating the full catalog.

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.