infrontofx-fivem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFRONTOFX_SKILL_ROOT | No | Absolute path to the installed infrontofx-skill root. Optional; without it, installed-skill retrieval/search, task context and template preview are disabled. | |
| INFRONTOFX_RESOURCES_ROOT | No | Absolute path to the FiveM resources root. Optional; without it, local resource inspection is disabled. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_infrontofx_topicsB | List FiveM guidance topics aligned with infrontofx-skill. |
| get_infrontofx_skillA | Read a selected reference directly from the installed infrontofx-skill, with a content digest. Requires INFRONTOFX_SKILL_ROOT; never reads arbitrary paths. |
| search_infrontofx_skillB | Find relevant house rules by literal terms across approved installed-skill references, with file and line locations. |
| compose_fivem_contextB | Read the installed house references needed for one coding workflow and optional NUI framework. Use before implementing or reviewing a FiveM resource. |
| preview_fivem_templateA | Preview source files from the installed canonical house shop example, with a validated resource/controller name. Does not write files or implement arbitrary requested features. |
| get_infrontofx_guidanceC | Read focused guidance. Existing project instructions and the installed infrontofx-skill remain authoritative for house conventions. |
| review_fivem_sourceA | Pattern-based advisory review of pasted Lua/NUI source. Does not execute code or prove security. Do not send credentials. |
| validate_fxmanifestA | Parse a pasted Lua manifest without executing it; inspect declared API, distribution and load order. Lua 5.3-compatible manifest syntax only. |
| inspect_fivem_resourceB | Read-only local triage inside INFRONTOFX_RESOURCES_ROOT. Skips secret-named files, private/build/vendor directories and symlinks. Returns findings, not raw files. |
| search_fivem_nativeA | Search the official GTA and Cfx native indexes by name/hash, with API-set filtering and source links. Network access only to two fixed official index URLs. |
| plan_fivem_resourceC | Return a house-style FiveM resource plan with explicit validation steps. Does not write files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| architecture | |
| security | |
| performance | |
| nui | |
| realtime | |
| database | |
| debugging | |
| networking |
TDQS
Scored across 11 tools
Most tools have distinct scopes (review, validate, inspect, search natives, plan, preview). However, get_infrontofx_skill, get_infrontofx_guidance, list_infrontofx_topics, and search_infrontofx_skill all read reference material, and an agent could easily misselect among them without close reading of the descriptions.
Consistent snake_case verb_noun pattern throughout (get_/list_/search_/compose_/preview_/review_/validate_/inspect_/plan_). Minor deviation: the domain prefix alternates between infrontofx_skill and fivem_*, and validate_fxmanifest lacks a prefix, but style is otherwise uniform.
11 tools is a well-scoped count for a guidance/review/planning surface. Slightly heavy only because the four reference-reading tools could arguably be consolidated.
Covers discovery, reference reading, context composition, planning, template preview, review, manifest validation, resource inspection, and native lookup — a coherent advisory lifecycle. Notably absent are any write/scaffold operations, though this appears deliberate given the read-only safety framing.