Skip to main content
Glama

resource_deploy

Destructive

Copies a workspace resource into a FiveM server's resource folder, skips shared resources, and can refresh and restart it to apply changes.

Instructions

Copy a workspace resource to a server's resource folder (no-op when shared) and optionally refresh and restart it

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_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
ensureNo
serverNo
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, so the write/mutation profile is known. The description adds genuinely useful behavior beyond that: the copy is a no-op when the resource is shared, and the tool can optionally refresh and restart the resource as a side effect. It does not say what existing files get overwritten or what the restart implies for a running server, leaving the destructive surface underspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler: the primary action comes first, then the no-op caveat, then the optional follow-up. The parenthetical interrupts the main clause slightly, but no sentence is wasted.

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 destructive, three-parameter tool with no annotations explaining what is destroyed and an entirely undocumented schema, the description is thin. It never states what the copy overwrites, whether the restart requires the resource to be stopped, or what ensure actually controls, which leaves real risk for an agent invoking it.

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 and largely fails to. The word "resource" maps to the required param and "a server's resource folder" implies the server param, but the third parameter, ensure (default true), is never named or explained — the phrase "optionally refresh and restart" hints at it without making the mapping or its default semantics clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Copy a workspace resource to a server's resource folder") plus a scoping caveat ("no-op when shared") and an optional follow-up action (refresh and restart). It clearly distinguishes itself from create/delete/edit siblings by describing a copy-to-server operation, though it never names an alternative tool explicitly.

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 when-to-use guidance, no prerequisites, and no exclusions relative to siblings like resource_create, resource_control, or dev_cycle. The only conditional stated ("no-op when shared") describes an internal behavior, not a use-case routing rule, so an agent must infer the appropriate context on its own.

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