Skip to main content
Glama

Loadster

by com.loadster
OverviewDiscussionsAdmin

Get Documentation

get_documentation
Read-onlyIdempotent

List the Loadster manual's topics with their keys and URLs, or read up to 3 topics' text by key. Pass one key as topic, or up to 3 keys as topics. Omit both to list every topic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoA single topic key, e.g. 'monitoring' or the nested 'playwright-scripts/bot'. Same as passing that one key in topics. Omit, and omit topics, to list every topic.
topicsNoUp to 3 topic keys, e.g. 'dynamic-datasets' or the nested 'playwright-scripts/bot'. Omit, and omit topic, to list every topic.
maxLengthNoCharacters to return per topic. Defaults to 25000.
startIndexNoCharacter offset to resume one topic from, taken from a previous call's nextStartIndex.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / topic
      Added value: +{
+  "description": "A single topic key, e.g. 'monitoring' or the nested 'playwright-scripts/bot'. Same as passing that one key in topics. Omit, and omit topics, to list every topic.",
+  "enum": [
+    "protocol-scripts",
+    "browser-scripts",
+    "playwright-scripts",
+    "code-blocks",
+    "variables-and-expressions",
+    "dynamic-datasets",
+    "analyzing-test-results",
+    "monitoring",
+    "browser-scripts/evaluate-blocks",
+    "cloud-regions",
+    "code-blocks/bot",
+    "code-blocks/browser",
+    "code-blocks/crypto",
+    "code-blocks/formats",
+    "code-blocks/http",
+    "code-blocks/json",
+    "code-blocks/xml",
+    "getting-started",
+    "incidents-and-notifications",
+    "integration-with-opsgenie",
+    "integration-with-pagerduty",
+    "integration-with-slack",
+    "integration-with-victorops",
+    "integration-with-webhooks",
+    "load-test-scenarios",
+    "load-testing-with-continuous-integration",
+    "loadster-cli",
+    "mcp",
+    "playwright-scripts/bot",
+    "playwright-scripts/organizing-scripts",
+    "protocol-scripts/capturing-rules",
+    "protocol-scripts/openapi-swagger",
+    "protocol-scripts/validation-rules",
+    "rest-api",
+    "running-load-tests",
+    "sso",
+    "status-pages",
+    "terms-and-definitions",
+    "testing-with-loadster-engine"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / topics / description
      Previous value: -"Up to 3 topic keys, e.g. 'dynamic-datasets' or the nested 'playwright-scripts/bot'. Omit to list every topic."New value: +"Up to 3 topic keys, e.g. 'dynamic-datasets' or the nested 'playwright-scripts/bot'. Omit, and omit topic, to list every topic."
  2. Changed1 schema field changed
    • changedInput schema / properties / topics / items / enum
      Previous value: -[
-  "protocol-scripts",
-  "browser-scripts",
-  "playwright-scripts",
-  "code-blocks",
-  "variables-and-expressions",
-  "dynamic-datasets",
-  "analyzing-test-results",
-  "monitoring",
-  "ai-agents",
-  "browser-scripts/evaluate-blocks",
-  "cloud-regions",
-  "code-blocks/bot",
-  "code-blocks/browser",
-  "code-blocks/crypto",
-  "code-blocks/formats",
-  "code-blocks/http",
-  "code-blocks/json",
-  "code-blocks/xml",
-  "getting-started",
-  "incidents-and-notifications",
-  "integration-with-opsgenie",
-  "integration-with-pagerduty",
-  "integration-with-slack",
-  "integration-with-victorops",
-  "integration-with-webhooks",
-  "load-test-scenarios",
-  "load-testing-with-continuous-integration",
-  "loadster-cli",
-  "playwright-scripts/bot",
-  "playwright-scripts/organizing-scripts",
-  "protocol-scripts/capturing-rules",
-  "protocol-scripts/openapi-swagger",
-  "protocol-scripts/validation-rules",
-  "rest-api",
-  "running-load-tests",
-  "sso",
-  "status-pages",
-  "terms-and-definitions",
-  "testing-with-loadster-engine"
-]New value: +[
+  "protocol-scripts",
+  "browser-scripts",
+  "playwright-scripts",
+  "code-blocks",
+  "variables-and-expressions",
+  "dynamic-datasets",
+  "analyzing-test-results",
+  "monitoring",
+  "browser-scripts/evaluate-blocks",
+  "cloud-regions",
+  "code-blocks/bot",
+  "code-blocks/browser",
+  "code-blocks/crypto",
+  "code-blocks/formats",
+  "code-blocks/http",
+  "code-blocks/json",
+  "code-blocks/xml",
+  "getting-started",
+  "incidents-and-notifications",
+  "integration-with-opsgenie",
+  "integration-with-pagerduty",
+  "integration-with-slack",
+  "integration-with-victorops",
+  "integration-with-webhooks",
+  "load-test-scenarios",
+  "load-testing-with-continuous-integration",
+  "loadster-cli",
+  "mcp",
+  "playwright-scripts/bot",
+  "playwright-scripts/organizing-scripts",
+  "protocol-scripts/capturing-rules",
+  "protocol-scripts/openapi-swagger",
+  "protocol-scripts/validation-rules",
+  "rest-api",
+  "running-load-tests",
+  "sso",
+  "status-pages",
+  "terms-and-definitions",
+  "testing-with-loadster-engine"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / topics / items / enum
      Previous value: -[
-  "protocol-scripts",
-  "browser-scripts",
-  "playwright-scripts",
-  "code-blocks",
-  "variables-and-expressions",
-  "dynamic-datasets",
-  "analyzing-test-results",
-  "monitoring",
-  "ai-agents",
-  "browser-scripts/evaluate-blocks",
-  "cloud-regions",
-  "code-blocks/bot",
-  "code-blocks/browser",
-  "code-blocks/crypto",
-  "code-blocks/formats",
-  "code-blocks/http",
-  "code-blocks/json",
-  "code-blocks/xml",
-  "getting-started",
-  "incidents-and-notifications",
-  "integration-with-opsgenie",
-  "integration-with-pagerduty",
-  "integration-with-slack",
-  "integration-with-victorops",
-  "integration-with-webhooks",
-  "load-test-scenarios",
-  "load-testing-with-continuous-integration",
-  "loadster-cli",
-  "playwright-scripts/bot",
-  "playwright-scripts/organizing-scripts",
-  "protocol-scripts/capturing-rules",
-  "protocol-scripts/openapi-swagger",
-  "protocol-scripts/validation-rules",
-  "running-load-tests",
-  "sso",
-  "status-pages",
-  "terms-and-definitions",
-  "testing-with-loadster-engine"
-]New value: +[
+  "protocol-scripts",
+  "browser-scripts",
+  "playwright-scripts",
+  "code-blocks",
+  "variables-and-expressions",
+  "dynamic-datasets",
+  "analyzing-test-results",
+  "monitoring",
+  "ai-agents",
+  "browser-scripts/evaluate-blocks",
+  "cloud-regions",
+  "code-blocks/bot",
+  "code-blocks/browser",
+  "code-blocks/crypto",
+  "code-blocks/formats",
+  "code-blocks/http",
+  "code-blocks/json",
+  "code-blocks/xml",
+  "getting-started",
+  "incidents-and-notifications",
+  "integration-with-opsgenie",
+  "integration-with-pagerduty",
+  "integration-with-slack",
+  "integration-with-victorops",
+  "integration-with-webhooks",
+  "load-test-scenarios",
+  "load-testing-with-continuous-integration",
+  "loadster-cli",
+  "playwright-scripts/bot",
+  "playwright-scripts/organizing-scripts",
+  "protocol-scripts/capturing-rules",
+  "protocol-scripts/openapi-swagger",
+  "protocol-scripts/validation-rules",
+  "rest-api",
+  "running-load-tests",
+  "sso",
+  "status-pages",
+  "terms-and-definitions",
+  "testing-with-loadster-engine"
+]
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description restates the 3-topic cap that is also in the schema and gestures at pagination only indirectly via startIndex; it adds little behavioral context beyond the structured fields.

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

Conciseness5/5

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

Two dense sentences, zero filler, with the listing mode and the read mode front-loaded before the parameter mechanics. Every clause earns its place.

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 docs retrieval tool with no output schema, the description covers both operating modes and enough parameter mechanics to call it correctly. It could be stronger by noting how it relates to the other documentation-style siblings.

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 the schema documents each parameter (including the topic/topics mutual role and the 25000-char default). The description's contribution is limited to reiterating the one-key vs three-key distinction already present in the property descriptions.

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?

The description names a specific verb+resource pair ('List the Loadster manual's topics... or read up to 3 topics' text by key') and clearly captures the tool's dual list/read mode. However, it never differentiates itself from documentation-adjacent siblings like get_scripting_api, get_command_schema, or get_example, leaving the agent to infer which reference tool 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 Guidelines4/5

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

It gives explicit mode-selection rules: pass one key as 'topic', up to 3 as 'topics', or omit both to list everything. What's missing is any guidance on when to reach for this tool versus the sibling schema/API/reference tools.

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

All Loadster toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources