laravel-skills-localsetup
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_guidelinesA | Returns procedural guidelines and domain rules for Laravel 13 local development setup. Args: section: Optional keyword to filter content sections. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_skill_resource | Provides the complete raw skill documentation as an MCP context resource. |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly distinct by default.
With a single tool, there is no mixed convention to evaluate. The name 'get_guidelines' follows a clean verb_noun pattern.
The server has only one tool, which feels thin for a domain that could warrant separate operations (e.g., listing sections, validating setup steps). However, for a simple guidelines retrieval server, one tool is borderline acceptable.
The single tool covers the primary need of retrieving procedural guidelines, but there are minor gaps such as an explicit way to enumerate available sections or get more granular support. Agents can likely work around these gaps.