laravel-skills-multilingual
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 multilingual and localization implementation. 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
With only a single tool, there is no possibility of overlapping purposes, and get_guidelines' role is immediately understandable.
The one tool name uses a clean verb_noun pattern, get_guidelines, and clearly signals an information-retrieval action.
A single tool feels thin for a skill server, though the narrow guidelines-only scope may justify it. There are no supplementary tools for listing or navigating sections.
The tool can retrieve all guidelines or filter by section, covering the main need for procedural and domain rules. No lifecycle operations are expected for a static knowledge resource, and an unfiltered call provides full access.