Skip to main content
Glama

test_create_scenario

Destructive

Store a named test scenario with ordered FiveM actions, delays, assertions on saved results, and cleanup steps for repeatable gameplay validation.

Instructions

Store a named test: ordered actions (any game operation, client_command or input), delays and assertions on saved results, plus cleanup steps

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

Input Schema

NameRequiredDescriptionDefault
scenarioYes

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, destructiveHint=true, and openWorldHint=false. The description is consistent with a write operation and adds real content by revealing that stored steps include assertions and cleanup steps — which plausibly explains the destructive flag, since cleanup can delete entities. It still omits whether storage overwrites, where scenarios persist, and whether the destructive hint applies at store time or only at execution time.

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 dense sentence with the core operation front-loaded and the detail clause following in sequence: steps, delays, assertions, cleanup. No filler, though the parenthetical "(any game operation, client_command or input)" reads slightly awkwardly.

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 tool with a deeply nested object schema, no output schema, and zero schema description coverage, the definition covers the top-level shape well enough to construct a call. It leaves out timeoutMs, item limits, and the binding/condition semantics, which an agent would have to reverse-engineer from the schema alone.

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% on a single deeply nested "scenario" parameter, so the description must carry the load. It correctly maps the step kinds (action, delay, assert) and the cleanup array, but says nothing about name, timeoutMs (default 30s, max 120s), the 40-step and 8-cleanup limits, or the bind/saveAs/when/participant mechanics that the schema exposes without prose.

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?

"Store a named test" gives a concrete verb plus resource, and the rest of the sentence enumerates what the stored artifact contains: ordered actions, delays, assertions, cleanup. It implicitly separates itself from test_execute_scenario by framing the operation as storage rather than execution, though it never names that sibling.

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?

The verb "Store" implies this is for persisting a scenario definition rather than running one, which is a useful hint against test_execute_scenario. However, there is no explicit when-to-use, no prerequisites, and no statement of what happens if a scenario with the same name already exists.

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