Skip to main content
Glama

inspect_dataset

Analyze a CSV dataset to reveal column types, missing values, summary statistics, and a preview, helping you assess data quality before preprocessing or modeling.

Instructions

Inspect a CSV dataset (types, missing values, stats).

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

Input Schema

NameRequiredDescriptionDefault
nameYesDataset filename.
max_rowsNoMax preview rows (default 25, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and it discloses very little: it never states that the operation is read-only, whether the whole file is scanned or sampled, or what happens with malformed CSV input. The parenthetical list of result categories is the only behavioral signal, which is thin for a file-reading tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler; every clause maps to real information about the tool. It is efficient, though the brevity contributes to the under-specification noted elsewhere rather than being a flaw in structure itself.

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

Completeness2/5

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

For a file-reading tool with no annotations and no output schema, the description should indicate the shape of results and any cost or read-scope behavior; it gives only a three-item parenthetical. An agent cannot tell how large the response is or whether the tool is safe and cheap to call repeatedly.

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%, with both 'name' and 'max_rows' documented including the default and maximum for preview rows, so the schema already does the heavy lifting. The description adds nothing about parameters beyond implying a preview, which matches the baseline of 3.

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 gives a specific verb plus resource ("Inspect a CSV dataset") and parenthetically enumerates the outputs (types, missing values, stats), so an agent knows exactly what the tool produces. It stops short of distinguishing itself from siblings such as analyze_data_quality or prepare_dataset, which likely overlap in scope.

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

Usage Guidelines2/5

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

There is no explicit statement of when to call this versus prepare_dataset or analyze_data_quality, nor any prerequisite or exclusion. The word "Inspect" only weakly implies a first-look exploratory step, leaving the routing decision to inference.

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