Loadster

Get Load Test Report

get_load_test_report

Read-onlyIdempotent

Get a finished Load Test's Test Report — aggregate totals, the error and advice picture behind the Dashboard's advice tile, per-Population outcomes, and each engine's average and peak CPU; an unfinished test answers with an error naming its status. The advice buckets and detection flags are heuristics, not a diagnosis of this test: where the totals, percentiles, per-URL counts and Populations contradict a bucket or a flag, or show something it never names, say so and follow the data. Before advising the user, read the get_documentation topic 'analyzing-test-results' and cross-read the Scenario and the played Scripts, so your advice names concrete elements — a specific URL, Population, bot count, or script step — instead of repeating the error buckets back.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_load_test_report"
  }
}

Input Schema

Name	Required	Description
`testId`	No	Deprecated alias of loadTestId; send loadTestId instead.
`projectId`	Yes
`loadTestId`	No	The load test id, as reported by list_load_tests. Required unless the deprecated testId is sent.
`errorUrlLimit`	No	How many URLs to return in errorsByUrl, worst first (default 10, no maximum). There is no offset, so read the tail by raising this.

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`notes`	No
`advice`	No
`engines`	No
`maxBots`	Yes
`startedAt`	No
`totalHits`	Yes
`finishedAt`	No
`scenarioId`	No
`totalPages`	Yes
`errorsByUrl`	Yes
`populations`	Yes
`totalErrors`	Yes
`dashboardUrl`	Yes
`errorUrlNote`	No
`scenarioName`	No
`stoppedEarly`	Yes
`playedScripts`	Yes
`responseTimes`	Yes
`totalErrorUrls`	Yes
`totalIterations`	Yes
`avgHitsPerSecond`	Yes
`maxHitsPerSecond`	Yes
`avgPagesPerSecond`	Yes
`maxPagesPerSecond`	Yes
`totalBytesTransferred`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 30, 2026

addedInput schema / properties / loadTestId

Added value: +{
+  "description": "The load test id, as reported by list_load_tests. Required unless the deprecated testId is sent.",
+  "type": "string"
+}

changedInput schema / properties / testId / description

Previous value: -"The load test id, as reported by list_load_tests."New value: +"Deprecated alias of loadTestId; send loadTestId instead."

changedInput schema / required

Previous value: -[
-  "projectId",
-  "testId"
-]New value: +[
+  "projectId"
+]

addedOutput schema / properties / engines

Added value: +{
+  "items": {
+    "properties": {
+      "avgCpuPercent": {
+        "format": "double",
+        "type": "number"
+      },
+      "name": {
+        "type": "string"
+      },
+      "peakCpuPercent": {
+        "format": "double",
+        "type": "number"
+      }
+    },
+    "required": [
+      "avgCpuPercent",
+      "name",
+      "peakCpuPercent"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedSep 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover read-only safety, but the description adds crucial behavioral context: unfinished tests return an error naming their status, advice buckets are heuristic not diagnostic, and the agent must reconcile buckets against the full data and name concrete elements. This goes well beyond what annotations provide.

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?

The description is front-loaded with the report contents and error behavior before moving to advice guidance. It is dense but every sentence adds value—the final sentence about cross-reading Scenario and Scripts is long but actionable. Slightly verbose but appropriate for a report tool.

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

Completeness5/5

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

Given the tool's complexity, annotations, and the presence of an output schema, the description is complete: it explains what is returned, error behavior for unfinished tests, the heuristic nature of the advice data, and how to use the report for user advice. Nothing critical is missing.

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 coverage is 75%, with descriptions for testId, loadTestId, and errorUrlLimit including detailed semantics in the schema. The tool description itself does not elaborate on parameter meaning beyond implying a finished test is required and the report's contents. Baseline 3 is appropriate since the schema carries the parameter semantics.

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 finished Load Test's Test Report') and enumerates exactly what the report contains: aggregate totals, advice context, per-Population outcomes, and per-engine CPU stats. This distinguishes it from sibling tools like get_load_test_status and get_load_test_url_timings without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly sets context: use for a finished test, and unfinished tests answer with an error naming their status, which implicitly tells the agent not to use this for status checks. It also instructs reading the 'analyzing-test-results' documentation and cross-reading Scenario/Scripts before advising. However, it does not explicitly name alternative tools (e.g., get_load_test_status) for incomplete tests.

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.