Loadster

Get Scenario

get_scenario

Read-onlyIdempotent

Get a single scenario including its Populations, plus a dashboard link and its launch readiness: the account's fuelBalance; launchBlockers, where an empty list means it can launch as it stands; and estimatedFuelLow and estimatedFuelHigh, the low and high ends of the Fuel estimate the Dashboard shows. The estimate is present whenever the test would burn Fuel, which is every test on an account without a plan, and on one with a plan, any test the plan does not cover; launch_load_test then runs the whole test on Fuel. Without an estimate, it runs on the account's plan and burns no Fuel. get_documentation topic 'faqs/plan-or-fuel' explains when a plan or Fuel applies. A field left out of a population is at its default: iterations and iterationsPerUser unlimited, aggressionMultiplier 1.0, and bandwidth unthrottled. Read get_documentation topic 'load-test-scenarios' for what the stages and ramps actually do.

Input Schema

Name	Required	Description	Default
`projectId`	Yes
`scenarioId`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`tags`	No
`maxBots`	Yes
`version`	No
`projectId`	Yes
`fuelBalance`	Yes
`populations`	Yes
`dashboardUrl`	Yes
`totalDuration`	Yes
`launchBlockers`	Yes
`populationCount`	Yes
`estimatedFuelLow`	No
`estimatedFuelHigh`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 31, 2026

removedOutput schema / properties / estimatedFuel

Removed value: -{
-  "format": "int32",
-  "type": "integer"
-}

addedOutput schema / properties / estimatedFuelHigh

Added value: +{
+  "format": "double",
+  "type": "number"
+}

addedOutput schema / properties / estimatedFuelLow

Added value: +{
+  "format": "double",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "dashboardUrl",
-  "estimatedFuel",
-  "fuelBalance",
-  "id",
-  "launchBlockers",
-  "maxBots",
-  "name",
-  "populationCount",
-  "populations",
-  "projectId",
-  "totalDuration"
-]New value: +[
+  "dashboardUrl",
+  "fuelBalance",
+  "id",
+  "launchBlockers",
+  "maxBots",
+  "name",
+  "populationCount",
+  "populations",
+  "projectId",
+  "totalDuration"
+]

Changed1 schema field changedOct 30, 2026
- addedOutput schema / properties / populations / items / properties / engineId
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedSep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds substantial domain behavior beyond that: how to interpret the Fuel estimate, when estimatedFuelLow/High is present, what launchBlockers means, and how omitted population fields default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the content is relevant, but the description becomes dense and rambling, especially the long conditional explanation of when a Fuel estimate is present. It is informative rather than wasteful, but some clauses could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only getter with an output schema and strong annotations, the description is complete enough: it explains the returned scenario contents, defaults, launch readiness, and documentation references. The main gap is that the required IDs are undocumented in both schema and description.

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 compensate for undocumented parameters, but it never mentions projectId or scenarioId or where to obtain them. The parameter names are self-evident, which prevents a 1, but the description adds essentially no parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: get a single scenario, including Populations, dashboard link, and launch readiness. It clearly distinguishes this from list_scenarios by emphasizing a single scenario, and it names concrete returned fields such as fuelBalance and launchBlockers.

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 implied by phrases like launchBlockers meaning it can launch as it stands, and by the downstream reference to launch_load_test. However, it never explicitly says when to use this tool versus list_scenarios or update_scenario, and it gives no exclusions for retrieval.

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

All Loadster tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.