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

laravel13-livewire4.2.1-mcp

by shamimlaravel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

generate_service_class

Generate a Laravel service class to encapsulate business logic like billing or notifications. Define methods with parameters and return types.

Instructions

Generate a Laravel service class for business logic (BillingService, NotificationService, etc.).

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": {
      "serviceName": "<serviceName>"
    },
    "name": "generate_service_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodsNo
serviceNameYesService name e.g. 'BillingService'

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, but it only states the action of generating a class. It does not disclose side effects like file creation, overwriting, need for existing directories, or return values. This lack of behavioral detail could lead to unexpected consequences.

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, front-loaded sentence with no redundant or filler words. It delivers the core purpose quickly and is easy to scan.

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 no output schema and incomplete parameter documentation, the description should provide more context. It lacks guidance on the methods parameter, expected file placement, or what constitutes a valid service class. This is insufficient for users to use the tool confidently.

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?

The schema describes serviceName, but methods is completely undocumented. The description does not mention methods at all, leaving half the parameters without meaning. The description's examples hint at naming conventions but do not explain how to define methods or their parameters.

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 clearly states the tool generates a Laravel service class for business logic, with concrete examples (BillingService, NotificationService). This verb+resource combination is specific and distinguishes it from sibling generators like generate_policy or generate_enum.

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 phrase 'for business logic' and the examples imply when to use this tool, but there is no explicit 'use this when' or any alternatives/exclusions. It relies on the user's inferential ability rather than providing direct guidance.

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