Skip to main content
Glama
Sign In
uikit-registry

uikit-registry

by captainy7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_component

Retrieve UI component details from libraries: source code for shadcn, props and examples for MUI, Chakra, and others.

Instructions

Ambil detail komponen dari library tertentu. Dapat source code (shadcn) atau props + contoh (MUI, Chakra, dll).

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>",
      "component": "<component>"
    },
    "name": "get_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
libraryYesLibrary UI: mui, chakra, shadcn, antd, mantine, nextui, radix, daisyui, primereact, neobrutalism, aceternity, magic-ui, origin-ui
componentYesNama komponen (contoh: button, dialog, pagination)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It hints at differencing output based on library (source code vs props+examples), but does not disclose response format, side effects, prerequisites, or error handling. Adequate but not detailed.

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?

Two concise sentences with no wasted words. The key information is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should explain return values. It partially does by distinguishing output types per library, but lacks details on structure, errors, or edge cases. For a simple 2-parameter tool, it is fairly complete.

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?

Schema coverage is 100% with clear parameter descriptions. The description adds value by explaining that for shadcn it returns source code, while for other libraries it returns props+examples, which enriches the semantic understanding beyond the schema.

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?

The description clearly states the verb 'Ambil' (get) and resource 'detail komponen' from a specific library. It distinguishes the type of details by library (source code for shadcn, props+examples for others), which helps differentiate from sibling tools like compare_components and search_component.

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 description implies usage for getting component details from a specific library, but does not explicitly state when to use this tool versus the siblings. No exclusions or alternative guidance is provided.

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