data-analysis-agent

by Soham-Donode

Overview Schema Source Related Servers Discussions Admin

Python

remove_duplicates

Eliminate duplicate rows from your dataset, optionally based on selected columns, with the ability to undo.

Instructions

Remove duplicate rows across all or a subset of columns. Reversible.

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

Input Schema

Name	Required	Default
`keep`	No	first
`subset`	No
`session_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.6/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 burden. It discloses that the operation is reversible, which is useful for a mutation tool. However, it does not mention whether session state is modified in place, any prerequisites, or other side effects.

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?

One short sentence with no filler. The key scoping phrase is front-loaded and the reversibility note adds value without extra length.

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

Completeness3/5

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

For a 3-parameter transformation with an output schema, the description gives the core behavior and reversibility, but lacks usage context and side-effect details. It is minimally adequate but not complete enough to fully guide agent selection and invocation.

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

Parameters2/5

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

Schema description coverage is 0%. The description only clarifies the 'subset' parameter by mentioning 'all or a subset of columns'. Parameters 'keep' and 'session_id' are left entirely to their schema properties, so the description does not compensate for the low coverage.

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?

States a specific action ('Remove duplicate rows') with a clear scope ('across all or a subset of columns') and adds reversibility. This clearly distinguishes it from sibling transformation tools such as drop_column or rename_column.

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?

No explicit when-to-use or alternative routing is provided, but the operation name strongly implies a data-cleaning/deduplication use case. There are no exclusions or comparisons to sibling tools.

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