Skip to main content
Glama
Sign In
AI-ML-Lab-MCP

AI-ML-Lab-MCP

by SyedHassan904
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Remove Duplicates

remove_duplicates

Removes duplicate rows from a dataset, keeping the first occurrence of each row. Returns row counts before and after plus the number of rows removed.

Instructions

Remove duplicate rows from a dataset (the first occurrence of each row is kept). Args: dataset_id (str): ID of the dataset. Returns: dict: rows before and after, and how many rows were removed.

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

Input Schema

NameRequiredDescriptionDefault
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the meaningful behavioral detail that the first occurrence is kept and that the return includes before/after row counts, but it never states whether the dataset is mutated in place or a new dataset is produced, nor whether the change is reversible.

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?

Front-loaded with the action and the dedup rule, followed by a compact docstring-style Args/Returns block. The parameter line is largely redundant with the schema, but nothing is bloated.

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 one-parameter tool with no output schema, the description covers what it does, the dedup policy, and the shape of the return value. The remaining gap — in-place mutation vs. new dataset — is the one thing an agent genuinely needs and doesn't get.

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 0%, and the description only restates `dataset_id (str): ID of the dataset` — the name and type are already in the schema, so no new meaning is added. For a single, self-evident parameter this is tolerable, but it fails the compensation standard.

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+resource ("Remove duplicate rows from a dataset") and adds a concrete rule about which copy survives ("the first occurrence of each row is kept"). It does not explicitly differentiate itself from the sibling `duplicate_rows`, but the action and outcome are unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when a dataset contains redundant rows. There is no statement of preconditions, no note on when to prefer `duplicate_rows` (detection) over this removal, and no warning about irreversibility.

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

Deploy Server

Other Tools