Skip to main content
Glama

resource_create

Destructive

Create a Lua or JavaScript FiveM resource with a manifest and client/server entry points by specifying a resource name and language.

Instructions

Create a Lua or JavaScript resource with a manifest and client/server entry points

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": {
      "resource": "<resource>"
    },
    "name": "resource_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNolua
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is supplied. The description adds useful context that the tool creates a manifest and client/server entry points, but it does not explain overwrite behavior, permission requirements, or what happens if the resource already exists.

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 wasted wording. It communicates the core action and scope efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with destructiveHint=true and no output schema, the definition is only partially complete. It states what gets created but omits important behavioral details such as overwrite semantics and expected outcomes.

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%, so the description must carry parameter meaning, but it only restates the language options already present as an enum and does not explain the resource parameter's naming pattern or the default language behavior. It adds little beyond the schema.

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 and resource ("Create a ... resource") and names the supported languages plus the manifest and client/server entry points it creates. This clearly distinguishes it from siblings like resource_edit, resource_delete, and resource_deploy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use guidance versus alternatives such as resource_edit, resource_deploy, or resource_list. It also omits prerequisites or conditions, leaving the agent to infer that this is strictly for initial creation.

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