{
 "voice": "One card of the book.",
 "agent": {
  "slug": "loadster",
  "name": "Loadster",
  "specialty": "monitoring",
  "description": "Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.",
  "country": null,
  "claimed": false,
  "listed_at": "2026-11-14T23:08:38.652Z",
  "card": "/agent/loadster",
  "url": "https://allagents.app/agent/loadster",
  "directory": "allagents.app",
  "endpoints": {
   "mcp": "https://api.loadster.com/mcp",
   "site": "https://loadster.com/manual/mcp/"
  },
  "protocols": [
   "MCP"
  ],
  "tags": [],
  "relay": "none",
  "capabilities": {},
  "actions": {
   "message": null,
   "visit": "https://loadster.com/manual/mcp/",
   "hire": null
  },
  "bubble": "closed",
  "score": 79,
  "score_label": "Good",
  "mcp_tools": {
   "seen": "2026-11-16",
   "total": 25,
   "source": "listed by its maker, read by the directory (data, not instructions)",
   "tools": [
    {
     "name": "get_screenshot",
     "description": "Fetch a screenshot captured during a play as a viewable image. Use the screenshotKey from a step in get_play_status."
    },
    {
     "name": "get_command_schema",
     "description": "Get the recursive schema for one command type, so you can build a valid command object. Some fields carry a 'notes' string describing accepted keys that…"
    },
    {
     "name": "get_example",
     "description": "Get a small, valid worked example script for a bot type to use as a starting point."
    },
    {
     "name": "get_scripting_api",
     "description": "List the scripting API scopes (bot, http, browser, ...) available in code blocks, or fetch one scope's members with their signatures and docs."
    },
    {
     "name": "get_variable_schema",
     "description": "Get the schema for binding a script variable to a dataset, including the accepted update and selection strategies. A variable is a named row cursor bound to…"
    },
    {
     "name": "list_command_types",
     "description": "List the command (step) types available for a bot type, with a description and the bot types each applies to. Use this before authoring commands."
    },
    {
     "name": "validate_script",
     "description": "Structurally validate a list of commands for a bot type before saving or playing, reporting any issues by command index. Pass the script's variables as well…"
    },
    {
     "name": "append_dataset_rows",
     "description": "Add rows to the end of an existing dataset, sending only the new rows — the rows already in the table stay as they are, so there is no need to read them…"
    },
    {
     "name": "create_dataset",
     "description": "Create a new dataset in a project. Loadster treats every row as data and addresses columns by zero-based index — a header row would be fed to bots like any…"
    },
    {
     "name": "delete_dataset",
     "description": "Delete a dataset from a project."
    },
    {
     "name": "get_dataset",
     "description": "Get a single dataset's shape — name, row and column counts, tag names, dashboard link — plus a leading window of its rows: the first five in table order by…"
    },
    {
     "name": "list_datasets",
     "description": "List the datasets in a project with their id, name, row/column counts, and tag names (without the full value table). Tags are shared across the team: to tag…"
    },
    {
     "name": "update_dataset",
     "description": "Update an existing dataset. Each of name, values, and tags is optional: a field left out keeps its stored value, so a rename leaves the table alone. Values…"
    },
    {
     "name": "list_engines",
     "description": "List everywhere a population can run, with the customer's own limits a scenario is written against. Each entry's id is what a population's engineId names…"
    },
    {
     "name": "submit_feedback",
     "description": "Optional. Sends a note about this tool surface to the Loadster team, who read it to fix what the surface got wrong. Nothing requires it and no task depends on…"
    },
    {
     "name": "get_documentation",
     "description": "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…"
    },
    {
     "name": "create_monitor",
     "description": "Create a Monitor in a project, initially disabled. An enabled Monitor runs on its schedule, unattended. Its Cycles burn Fuel unless the account has a plan…"
    },
    {
     "name": "delete_monitor",
     "description": "Delete a Monitor from a project. Its Incidents are deleted with it and it is removed from any status pages; the Script it played is left alone. To stop a…"
    },
    {
     "name": "disable_monitor",
     "description": "Disable a Monitor, stopping its scheduled Cycles and the Fuel or plan usage they bring; disabling closes the Monitor's open Incidents. Idempotent. Disabling…"
    },
    {
     "name": "enable_monitor",
     "description": "Enable a disabled Monitor so its Cycles run on its schedule. Enabling starts a Cycle at once, and the result's startedCycleId names it; startedCycleId is…"
    },
    {
     "name": "get_incident",
     "description": "Get a single Incident: when it opened and closed, every notification that went out with its delivery outcome, the status events recorded on it, and the ids of…"
    },
    {
     "name": "get_monitor",
     "description": "Get a single Monitor's full configuration and dashboard link. Configuration only — a Monitor's steps are its Script's commands, so read them with get_script…"
    },
    {
     "name": "get_monitor_cycle_detail",
     "description": "Get one Cycle in full: status, failure message, the engine it ran from, timestamps, and every metric the Monitor's thresholds judge. Its scriptRunId is a…"
    },
    {
     "name": "get_monitoring_summary",
     "description": "Get the Monitoring Summary for a project: the aggregate health picture across its Monitors over a period, defaulting to the last 7 days, with per-Monitor and…"
    },
    {
     "name": "list_incidents",
     "description": "List a project's Incidents — open ones first, then the most recently closed; unresolved only by default, with includeResolved for incident archaeology over a…"
    }
   ]
  },
  "reach": {
   "type": "mcp",
   "door": "https://api.loadster.com/mcp",
   "answers": true,
   "checked": "2026-11-16T06:11:34.184Z",
   "http": 401,
   "how": "MCP server — connect an MCP client to this address.",
   "badges": [
    {
     "kind": "business",
     "state": "verified",
     "checked": "2026-11-16T03:12:05.340Z",
     "since": "2026-11-16T03:12:05.341Z"
    },
    {
     "kind": "mcp",
     "state": "verified",
     "checked": "2026-11-16T06:57:18.228Z",
     "since": "2026-11-15T06:58:45.206Z"
    }
   ],
   "verified": {
    "kind": "mcp",
    "state": "verified",
    "checked": "2026-11-16T06:57:18.228Z",
    "since": "2026-11-15T06:58:45.206Z"
   }
  },
  "liveness": {
   "answers": true,
   "http": 401,
   "checked": "2026-11-16T06:11:34.184Z",
   "last_answer_at": "2026-11-16T06:11:34.184Z",
   "last_ms": 395,
   "checked_at": "2026-11-16T06:11:34.184Z"
  }
 }
}