Skip to main content
Glama

test_execute_scenario

Destructive

Runs a stored scenario by mapping participant names to opted-in player IDs, optionally waiting for completion, so you can test FiveM gameplay flows.

Instructions

Run a stored scenario with participant names mapped to opted-in player IDs

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": {
      "scenario": "<scenario>",
      "participants": "<participants>"
    },
    "name": "test_execute_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
serverNo
scenarioYes
participantsYes

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 declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the definition need not re-state that this mutates state. It does add genuinely new context by noting participants must be opted-in player IDs, but it says nothing about what gets destroyed or changed in the running game, nor about the blocking behavior implied by the wait parameter.

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 that wastes no words and puts the resource and the notable participant-mapping behavior first. It is efficient, though its brevity is achieved partly by omitting information the agent needs.

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, four-parameter tool with no output schema and zero schema description coverage, one sentence is thin. An agent still cannot tell whether the call blocks until the scenario finishes, which server is targeted by default, or what it gets back after firing a destructive scenario against live players.

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 the load for four parameters. It adds real meaning for scenario (must be stored) and participants (names as keys mapped to player IDs), but 'wait' and 'server' are entirely unexplained, and 'server' is a pattern-constrained string whose selection semantics matter a lot for a destructive test run.

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?

Specific verb (run) plus resource (a stored scenario) and an unusual detail that distinguishes it: participant names are mapped to opted-in player IDs. That separates it from test_create_scenario and test_run_regression, though it never names those siblings 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?

Only implied guidance: the word 'stored' hints a scenario must exist first, but there is no statement of when to use this versus test_create_scenario (to author) or test_get_results (to inspect outcomes), and no prerequisites such as player opt-in being required beforehand.

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