Skip to main content
Glama
Sign In
aceternity-mcp

aceternity-mcp

by dvnold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_component

Retrieve detailed metadata and full description for any Aceternity UI component by providing its slug. Includes dependencies, props, compatibility, and install commands.

Instructions

Get the full detailed entry for a single component.

Returns ALL metadata including the 60+ word detailed description, purpose, behavior, visual characteristics, dependencies, install commands, props, compatibility, and scoring.

Args: slug: Component slug (e.g. "spotlight", "bento-grid", "hero-parallax")

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

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It implies a read-only operation by stating 'Get...entry,' but does not explicitly confirm non-destructiveness, idempotency, or any side effects. Adequate for a simple retrieval, but lacks depth.

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?

The description is concise, with the core purpose in the first sentence, followed by a bullet-like list of return contents. The Args line is efficient. No redundant or unnecessary text.

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?

Given the tool's simplicity (one required parameter) and the presence of an output schema, the description adequately covers the input semantics and return scope. It could mention error conditions but is still sufficient for correct usage.

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 description adds concrete examples for the slug parameter (e.g., 'spotlight'), which is not present in the schema. With 0% schema description coverage, this compensates well and clarifies usage beyond the raw type definition.

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 clearly states the tool retrieves full details for a single component using a slug. It distinguishes from sibling tools that list or search components, though it does not explicitly name alternatives.

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 minimal guidance on when to use this tool vs. alternatives like list_components or search_components. It implies use for a single component but lacks explicit context or exclusions.

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