Skip to main content
Glama
Hyperiux-Immersion-Labs

Hyperiux MCP Server

Official

List Hyperiux Vault Effects

hyperiux_list_effects
Read-onlyIdempotent

Search or browse the Hyperiux Vault catalog of React/Next.js interaction effects. Filter by name or category to find scroll effects, cursor trails, WebGL scenes, and more.

Instructions

Browse or search the Hyperiux Vault catalog of React/Next.js interaction effects (scroll systems, cursor trails, WebGL scenes, animated buttons, page transitions, etc).

Does NOT return which effects are Pro vs Free - the catalog index this reads from doesn't carry that field today. Use hyperiux_get_effect on a specific slug to check its tier before assuming it's installable without a Hyperiux Pro account.

Args:

  • query (string, optional): substring match against effect name

  • category (string, optional): filter to one category slug

  • limit (number, default 30, max 100)

  • offset (number, default 0)

Returns JSON: { total, count, offset, effects: [{ name, category, categories, dependencies, version }], has_more, next_offset? }

Examples:

  • "What cursor effects are available?" -> category="cursor"

  • "Is there anything with 'particles' in the name?" -> query="particles"

  • Don't use when: you need one effect's full description/props/tier - use hyperiux_get_effect instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return.
queryNoCase-insensitive substring match against effect name (e.g. 'cursor', 'text-reveal'). Omit to list all.
offsetNoNumber of results to skip for pagination.
categoryNoFilter to one category, e.g. 'text', 'cursor', 'webgl', 'buttons', 'carousels', 'components', 'navigation', 'backgrounds', 'loaders', 'transitions'. Use hyperiux_list_categories to see all valid values with counts.
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent, so the safety profile is covered. The description adds important behavioral context beyond annotations: it discloses that the listing does NOT include Pro vs Free status and warns agents not to assume installability. It also documents the exact JSON return shape since no output schema exists.

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 well-structured with clear sections: purpose, key limitation, args, return shape, examples, and when-not-to-use. Every sentence adds information an agent needs, and the critical caveat about Pro vs Free is front-loaded.

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

Completeness5/5

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

Given there is no output schema, the description fully covers the return format including pagination fields like total, count, offset, has_more, and next_offset. It also handles the main ambiguity (tier status) and guides the agent to sibling tools for missing information, making it complete for correct invocation.

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%, so the baseline is 3. The description adds value by pairing natural-language intents with parameter usage ('What cursor effects are available?' -> category='cursor'), which helps an agent translate user requests into correct arguments. It also summarizes defaults, though most details are already in 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 states a specific verb ('browse or search') and a clear resource ('Hyperiux Vault catalog of React/Next.js interaction effects'), and it enumerates representative effect types. It also distinguishes itself from siblings by explicitly directing detail/tier lookups to hyperiux_get_effect and category discovery to hyperiux_list_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete natural-language usage examples, explains when to use query vs category, and explicitly says 'Don't use when: you need one effect's full description/props/tier - use hyperiux_get_effect instead.' This is explicit routing with alternatives and conditions.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hyperiux-Immersion-Labs/hyperiux-components'

If you have feedback or need assistance with the MCP directory API, please join our Discord server