laravel13-livewire4.2.1-mcp

Overview Schema Source Related Servers Discussions Admin

generate_project_structure

Generate complete Laravel 13 + Livewire project structure for enterprise, SaaS, or API apps, including all files, configs, and routes.

Instructions

Generate complete enterprise/SaaS/API Laravel 13 + Livewire project structure with all files, configs, and routes.

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": {
      "projectName": "<projectName>"
    },
    "name": "generate_project_structure"
  }
}

Input Schema

Name	Required	Default
`type`	No	enterprise
`features`	No
`projectName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0Aug 9, 2026

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 of behavioral context. It states the outputs (files, configs, routes) but does not disclose whether it overwrites existing files, requires a pre-existing Laravel installation, or has side effects. This is a significant gap for a scaffolding tool.

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, concise sentence that conveys the core purpose without unnecessary filler. Every word adds value, and the structure is front-loaded with the action and scope.

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 of this complexity (generating an entire project structure), the description is far too sparse. It lacks information about return values, side effects, prerequisites, or what specific files and routes are included. The absence of an output schema and annotations makes this gap more damaging.

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?

Schema description coverage is 0%; the description does not explain projectName or features. It partially clarifies the 'type' parameter by listing enterprise/SaaS/API values, but does not provide enough semantic guidance for the required projectName or the features array.

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 clearly specifies the resource: a complete enterprise/SaaS/API Laravel 13 + Livewire project structure including files, configs, and routes. This distinguishes it well from sibling tools that generate individual components or policies.

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 when a full project scaffold is needed, but does not explicitly state when to use this versus alternatives like generate_layout or install_laravel. There are no clear exclusion criteria or cross-references to sibling tools.

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

Deploy Server