Skip to main content
Glama

resource_control

Destructive

Start, stop, or restart a FiveM server resource and verify its new state to confirm the control action succeeded.

Instructions

Start, stop or restart a resource on the server and verify its new state

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>",
      "action": "<action>"
    },
    "name": "resource_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
serverNo
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state. The description adds that the tool verifies the resulting state, which is useful, but it does not disclose consequences such as in-flight work being interrupted by a stop/restart, required permissions, or whether the call blocks until the resource is healthy.

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?

A single sentence with the action set and the verification outcome front-loaded; every clause carries information and there is no padding.

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 three-parameter destructive mutation with no output schema, the definition covers the core action and hints that the resulting state is returned. It is thin on the undocumented "server" parameter and on the risk profile of stopping or restarting, leaving real gaps for an agent acting without supervision.

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 does not. The action and resource names are hinted at, but the third parameter, "server", is never explained — an agent gets no guidance on whether it identifies a target host, a logical scope, or a default when omitted.

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?

The description uses specific verbs (start, stop, restart) against a named resource and adds a verification outcome, so an agent can distinguish it from resource_create, resource_delete and resource_edit. It stops short of naming those siblings explicitly, but the operation is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the verb set: call it when a resource needs its lifecycle state changed. There is no explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as the resource already existing or being in a particular state before a restart.

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