Skip to main content
Glama

Stat Load Data

stat_load_data

Load tabular data from CSV, TSV, Excel, JSON, Parquet, or SPSS files into the session under a reusable name for subsequent statistical analysis.

Instructions

Load a tabular dataset (CSV/TSV/Excel/JSON/Parquet/SPSS) into the session.

Use this as the first step for any dataset stored as a file. The loaded object is stored under name and every other tool refers to it by that name.

When to use: at the start of an analysis session, once per dataset. When NOT to use: if the data are already in the session (check with stat_session_info first), or if you need to construct a small example — use stat_make_dataframe instead.

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": {
      "path": "<path>"
    },
    "name": "stat_load_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSession name to store the DataFrame under (default "df").df
pathYesPath to the file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: the data become session state stored under `name`, and every other tool references it by that name. It does not cover edge cases an agent might hit, such as name collisions/overwrite behavior, path resolution, or failure modes for unreadable files, which keeps it below a 5.

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?

The purpose is front-loaded in the first sentence, followed by compact blocks for state semantics and when/when-not guidance. Every sentence adds information and there is no filler.

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?

For a two-parameter ingestion tool with an output schema, the description covers the things an agent needs: what it ingests, that it creates session state, how to reference that state later, and when to avoid it. Return values need not be documented given the output schema.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning: it explains that `name` is the session handle used by all subsequent tools, which clarifies why the parameter matters and what the default implies in practice. The `path` parameter's file-format implications are covered by the format list rather than the schema.

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 opens with a specific verb and resource ('Load a tabular dataset') and enumerates the supported file formats, which makes the tool instantly identifiable. It is clearly distinct from siblings like stat_make_dataframe and stat_session_info by name and by function.

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

Usage Guidelines5/5

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

It states explicitly when to use ('at the start of an analysis session, once per dataset') and when not to use, including how to check first (stat_session_info) and which sibling to use for a different need (stat_make_dataframe). No alternatives or exclusions are left to inference.

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