Skip to main content
Glama

test_run_regression

Destructive

Run multiple stored scenarios in sequence and report each outcome, enabling repeatable regression checks for FiveM resources with defined participants.

Instructions

Run several stored scenarios in order and report each outcome

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": {
      "scenarios": "<scenarios>",
      "participants": "<participants>"
    },
    "name": "test_run_regression"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNo
scenariosYes
participantsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing about what is actually mutated (game/world state?), whether a mid-run failure aborts the remaining scenarios, or how long execution takes — significant gaps for a destructive batch operation.

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 well-formed sentence with the action and scope front-loaded and no filler. It is appropriately tight but too terse given how much undocumented surface it leaves.

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 tool with a nested participants object, 0% schema coverage, and no output schema despite promising to 'report each outcome', the definition is under-specified. It should at minimum describe the participants structure and the shape of the per-scenario result.

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% across three parameters, so the description carries the full burden and mostly fails: it hints at an ordered scenario list but never explains the server parameter or the participants map (a nested object of name-to-integer values). An agent must guess what participants keys and values mean.

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: run stored scenarios in order and report each outcome. It implies batch semantics distinct from a single-scenario executor (test_execute_scenario), but never names that sibling, so differentiation is left to inference.

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 only implied by 'several stored scenarios' — an agent can infer this is for multi-scenario batches that must already exist. There is no explicit when-to-use vs test_execute_scenario, no prerequisite statement (scenarios must be created first), and no guidance on failure handling or when a single run is preferable.

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