Skip to main content
Glama
Sign In
laravel13-livewire4.2.1-mcp

laravel13-livewire4.2.1-mcp

by shamimlaravel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

generate_flux_component

Generate Livewire Flux UI components with dark mode support. Configure the component type, variant, size, slots, and content to output ready-to-use code.

Instructions

Generate a Livewire Flux UI component using the official Flux component library with dark mode support.

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": {
      "componentName": "<componentName>"
    },
    "name": "generate_flux_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
slotsNo
contentNoComponent content/text
variantNo
fluxTypeNobutton
componentNameYesComponent name e.g. 'user.profile'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.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 the full burden for behavioral disclosure. It does not explain side effects, whether it creates or overwrites files, or how it integrates with the project. It only mentions dark mode support as a feature, which is not enough 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?

The description is a single, efficient sentence with no filler. It front-loads the core purpose and a key feature, making it appropriately sized and well-structured.

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

Completeness2/5

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

For a tool with 6 parameters, no annotations, and no output schema, the description is too sparse. It omits the available fluxType choices, variant semantics, and behavioral context, making it insufficient for correct invocation in many cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 33% of parameters have schema descriptions (componentName and content), and the description does not elaborate on fluxType, variant, size, or slots. The user must infer meaning from enum names, leaving ambiguity (e.g., slots).

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 uses the specific verb 'Generate' with the resource 'Livewire Flux UI component' and specifies the official Flux library and dark mode support. This clearly distinguishes it from the sibling generate_livewire_component and other component generators.

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 creating Flux components but does not state when to choose this tool over alternatives like generate_livewire_component or convert_html_to_livewire. It also does not mention exclusions, so usage context is only implicit.

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