Skip to main content
Glama
Sign In
@forgespace/ui-mcp

@forgespace/ui-mcp

Official
by Forge-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_available_components

Retrieve all components from a specified UI library, such as shadcn, radix, headlessui, material, or primevue, for use in project integration.

Instructions

List all available components for a given component library (shadcn, radix, headlessui, material).

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": {
      "library": "<library>"
    },
    "name": "get_available_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
libraryYesComponent library

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.25.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states it 'list all available components' with no disclosure of behavioral traits like idempotency, rate limits, or return format. While the action is simple and non-destructive, the description lacks explicit transparency.

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 sentence that is concise and front-loaded with the key action and resource. No unnecessary words. Every part of the description adds value.

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 is adequate for a simple list tool with one parameter, but it lacks information about what the output looks like (e.g., list of component names or IDs). Given there is no output schema, completeness is moderate. The description does not specify any constraints or edge cases.

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?

The input schema has 100% coverage with a description for the 'library' parameter. The tool description adds no additional per-parameter semantics beyond what the schema provides, so baseline 3 applies. The description reinforces the parameter's purpose but does not add new detail.

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

Purpose5/5

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

Description clearly states the action (list), resource (available components), and scope (for a given component library). It specifies the supported libraries (shadcn, radix, headlessui, material) which distinguishes it from sibling tools like get_available_libraries that list libraries themselves.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It implies usage for listing components but does not state prerequisites, limitations, or when to use other tools like setup_component_library or validate_component_library_setup.

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

Deploy Server

Other Tools