laravel13-livewire4.2.1-mcp

Overview Schema Source Related Servers Discussions Admin

generate_trait

Generate reusable PHP traits for Laravel models to implement common behaviors: slug generation, tenant scoping, sorting, status fields, UUID keys, caching, and media handling.

Instructions

Generate a reusable PHP trait for Laravel models (HasSlug, HasTenant, Sortable, HasStatus, HasUuid, Cachable, HasMedia).

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": {
      "traitName": "<traitName>"
    },
    "name": "generate_trait"
  }
}

Input Schema

Name	Required	Description	Default
`traitName`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral details on its own. It only states the generation action and lists trait names, but omits critical behaviors such as whether it creates a file, overwrites existing files, or requires an existing Laravel project. No side-effect information is given.

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 sentence that is front-loaded with the action, and the parenthetical adds useful detail without bloat. Every word contributes to understanding the tool's core function.

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?

With no output schema and no annotations, the description needs to cover behavioral and parameter semantics fully. It fails to clarify the 'description' parameter's purpose, file output expectations, or project prerequisites, making it insufficient for a non-trivial code generation tool.

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 description lists the enum values for traitName in parentheses, which adds meaning beyond the bare schema enum. However, the optional 'description' parameter is not explained at all, leaving a gap given the 0% schema description coverage.

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 a specific verb 'Generate' and identifies the resource as 'a reusable PHP trait for Laravel models', listing the exact available trait names. This distinguishes it clearly from sibling generation tools like generate_policy or generate_eloquent_model.

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 context (when you need a trait for Laravel models) but provides no explicit guidance on when to choose this tool versus alternatives, nor any exclusions. The parenthetical list of trait names hints at scope, but no 'use this instead of X' statement is present.

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

Deploy Server