Loadster

Create Dataset

create_dataset

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 other row, so don't add one when authoring values. Unless the user explicitly asked for a dataset, confirm with them before creating one.

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>",
      "dataset": "<dataset>"
    },
    "name": "create_dataset"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Tag names; a name the team doesn't have yet becomes a new tag. Omit for no tags.
`dataset`	Yes	The dataset name and table of values (data rows only — no header row).
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / tags

Added value: +{
+  "description": "Tag names; a name the team doesn't have yet becomes a new tag. Omit for no tags.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedSep 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (non-readonly, non-destructive, non-idempotent, closed-world), so the bar is lower, and the description still adds substantive behavior: rows are treated as pure data, columns are addressed by zero-based index, and a header row would be ingested as a bot-visible row. It omits what happens on duplicate names or missing permissions, and the non-idempotent hint is never explained in prose.

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?

Three sentences, front-loaded with purpose, then the non-obvious data-format caveat, then the confirmation rule. No filler, and the most failure-prone detail (header rows) is placed before any optional context.

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 three-parameter mutation tool with a nested object and no output schema, the definition covers purpose, the critical table-format gotcha, and the confirmation guard. Missing pieces are the meaning/derivation of projectId and duplicate-name behavior, which leave some risk for an agent composing the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description compensates where it matters most by clarifying that `dataset.values` must contain data rows only with no header — a rule the schema does not state. `projectId` remains undocumented in both description and schema, and the nested structure's relationship to projectId is left implicit, keeping this below a 5.

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 ("Create a new dataset in a project"), which cleanly separates it from sibling tools such as append_dataset_rows, update_dataset, and get_dataset. It stops short of explicitly naming those siblings, so an agent must infer the boundary rather than read it.

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?

Gives a concrete precondition for invocation: confirm with the user unless they explicitly asked for a dataset. That is real when-to-use guidance. It does not address the create-vs-append decision (when an existing dataset should be extended with append_dataset_rows instead), which is the most likely misuse path.

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.