Skip to main content
Glama

dev_cycle

Destructive

Run a build-refresh-verify loop for a FiveM resource: build it, restart and wait, then report new server and client errors. Optionally open its UI and capture a screenshot.

Instructions

Edit-verify loop for one resource: run its npm build (if it has one), refresh and restart it, wait, then report new server and client errors. Optionally run a client command to open its UI and return a screenshot.

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": "dev_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNo
buildNoauto
playerNo
serverNo
resourceYes
settleMsNo
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real value beyond that by disclosing the concrete side effects (npm build, refresh and restart) and that it reports 'new' server and client errors after a settle period. Gaps remain: it does not say what a restart does to live connections or in-memory state, whether the build failure aborts the loop, or what the error report looks like. No contradiction with annotations.

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?

Two tight sentences that front-load the core purpose and then enumerate the pipeline in execution order. Every clause carries information; only the optional UI/screenshot step is slightly compressed relative to its nested object parameter.

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 7-parameter, destructive, multi-step orchestration tool with no output schema and no annotation detail beyond flags, the description covers the happy path but omits prerequisites (resource must exist, server must be running), failure/abort semantics, and the shape of the returned error report. Adequate to recognize the tool, thin for calling it confidently across its full parameter set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 all parameter meaning and it only partially does: it explains build ('if it has one' maps to auto/skip), open ('run a client command to open its UI'), screenshot ('return a screenshot'), and loosely hints at settleMs ('wait'). It says nothing about the required resource parameter's accepted form, nor about server or player, which are entirely undocumented in both schema and description.

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 names a concrete composite operation on a specific target: an 'edit-verify loop for one resource' with an enumerated pipeline (build, refresh/restart, wait, report errors, optional UI open + screenshot). That is far more specific than a bare verb+resource, and the pipeline shape differentiates it from single-purpose siblings like resource_control or resource_deploy. It stops short of 5 because it never explicitly contrasts itself with those siblings.

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?

'Edit-verify loop' implies the usage context (after editing a resource, to check for regressions), and 'if it has one' / 'optionally' signal conditional steps. However, there is no explicit when-to-use statement, no when-not to use it, and no pointer to which sibling to pick if the agent only wants a restart (resource_control) or only diagnostics (resource_get_diagnostics).

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