Skip to main content
Glama

Elementum Design System MCP

get_component_maturity

Returns machine-readable package version, component count, stability tier, and browser/testing verification metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_component_maturity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 disclosure burden. 'Returns' implies a read-only operation, and the field list hints at what comes back, but there is nothing about whether the metadata is static or cached, how freshness of the 'browser/testing verification metadata' is determined, or whether it can be empty/stale. For an unannotated tool this is thin behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler, and the verb plus payload are front-loaded. Nothing is repeated or wasted.

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?

There is no output schema, so the description is the only documentation of the response, and it does enumerate the four returned fields. It stops short of explaining their shapes or the possible values of 'stability tier', and it never clarifies scope, which is the main thing an agent needs before calling it.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description adds nothing misleading about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete return payload (package version, component count, stability tier, verification metadata), which is more than a restatement of the name. However it never states the scope of the resource being described — whether it reports on the whole component library or a single component — which is the key ambiguity for a zero-parameter tool whose name implies a per-component query. Sibling get_component_doc presumably takes a component identifier; this one does not, and the difference is left unexplained.

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 guidance on when to call this versus list_components, get_component_doc, or validate_component_usage. No preconditions, no mention of when the result should be trusted or refreshed. The reader must infer the use case entirely from the return payload.

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.