Skip to main content
Glama

clean_dataset

Clean datasets by handling missing values and outliers using customizable strategies like imputation, removal, or capping. Prepare data for analysis with methods such as KNN, IQR, or Z-score.

Instructions

Clean dataset by handling missing values and outliers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_nameYesName of the dataset to clean
missing_strategyNoStrategy for handling missing values (supports both full names and short aliases)
outlier_strategyNoStrategy for handling outlierscap
outlier_methodNoMethod for outlier detection (supports both full names and short aliases)iqr
missing_constant_valueNoValue to use when missing_strategy is fill_constant
missing_drop_thresholdNoProportion of missing values above which to drop columns/rows
missing_knn_neighborsNoNumber of neighbors for KNN imputation
missing_max_iterNoMaximum iterations for iterative imputation
missing_random_stateNoRandom seed for reproducible imputation
outlier_z_thresholdNoZ-score threshold for outlier detection
outlier_iqr_multiplierNoIQR multiplier for outlier detection
outlier_contaminationNoExpected contamination ratio for isolation forest and LOF
outlier_percentile_lowerNoLower percentile bound for percentile-based outlier detection
outlier_percentile_upperNoUpper percentile bound for percentile-based outlier detection
outlier_dbscan_epsNoDBSCAN epsilon parameter
outlier_dbscan_min_samplesNoDBSCAN minimum samples parameter
handle_missing_firstNoHandle missing values before outlier detection
preserve_originalNoPreserve original dataset alongside cleaned version
output_nameYesName for the cleaned dataset
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as whether the operation is destructive, if the original dataset is modified, or what side effects occur. This is a significant gap for a tool with 19 parameters and no output schema.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure. It does not front-load key information or expand on the tool's purpose, making it too brief given the tool's complexity.

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?

Given the tool's 19 parameters, lack of annotations, and no output schema, the description is severely incomplete. It provides no context on the cleaning process, expected output, or behavioral constraints, leaving the agent underinformed.

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?

The input schema has 100% description coverage, so the schema already documents all parameters. The tool description adds no extra semantic context beyond restating 'handling missing values and outliers', hence a baseline score of 3 is appropriate.

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 clearly states the tool's action (clean), resource (dataset), and specific scopes (missing values and outliers). This effectively distinguishes it from sibling tools like profile_dataset or validate_dataset, which serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives or when not to use it. It does not mention prerequisites, workflows, or exclusions, leaving the agent to infer usage context from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yasserelhaddar/MCP-DS-Toolkit-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server