Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

run_stress_test

Run a stress test scenario for a chosen duration and collect performance data over time to assess Godot project behavior under load.

Instructions

Run a stress test scenario and collect performance data over time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_stress_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationNoTest duration in seconds (default: 10)
scenarioNoOptional stress test scenario descriptor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not say whether the run blocks, how results are retrieved (e.g. via get_test_results), what resource load it imposes, or what happens to data between runs, leaving a mutating/expensive-sounding operation poorly characterized.

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 with no filler, and the action and outcome appear in the first clause. Its brevity is efficient, though it borders on under-specification rather than crisp conciseness.

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 tool with a nested scenario descriptor and no output schema, the description needs to explain where collected performance data goes and how to retrieve it. Neither point is addressed, so an agent cannot tell what a successful call yields.

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 100%, so both parameters are already documented, giving a baseline of 3. The phrase 'over time' loosely implies that duration governs the sampling window, but the description adds no syntax or structure for the nested scenario object beyond the schema.

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 a stress test scenario, plus an outcome (collect performance data over time). This is clearer than a tautology, but it never distinguishes itself from the sibling run_test_scenario, leaving the agent unsure which to pick.

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?

The description gives no when-to-use guidance, no prerequisites, and no indication of when run_test_scenario would be preferred instead. The agent must infer the selection criteria entirely from the tool name.

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

Deploy Server

Other Tools