Skip to main content
Glama

Remove duplicate CSV rows

toolfound_csv_deduplicator
Read-onlyIdempotent

Clean repeated campaign or listing-export rows while retaining the first exact match and showing how many rows changed. Returns an evidence-bounded result and the canonical web tool URL.

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

Input Schema

NameRequiredDescriptionDefault
csvYesCSV text whose first line is the header row, for example a campaign or listing export. Rows that exactly repeat an earlier row are dropped and the first copy is kept.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / csv / description
      Added value: +"CSV text whose first line is the header row, for example a campaign or listing export. Rows that exactly repeat an earlier row are dropped and the first copy is kept."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds genuinely new behavior: exact-match dedup semantics with first-copy retention and reporting how many rows changed. It also notes the response carries an evidence-bounded result plus a canonical web URL, which the annotations do not say. It omits the 12,000-character input ceiling, though the schema documents that.

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?

Two sentences, with the retention rule and the row-count feedback front-loaded and no filler. The phrase 'evidence-bounded result' is vague jargon that costs a little clarity without conveying concrete meaning.

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, read-only transform with an output schema, the description covers the essential contract: what gets removed, what gets kept, and that a change count is reported. Since return shape is documented by the output schema, the only residual gap is the input size ceiling, which the schema already states.

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?

There is a single required parameter and schema coverage is 100%, so the schema already explains that the first line is a header and that exact repeats are dropped. The description adds no format, quoting, or size guidance beyond that, so the baseline of 3 applies.

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 names a specific operation (deduplicating rows in campaign or listing-export CSVs) and a precise rule: the first exact match is retained. That is more specific than the title alone, though it never points at a sibling such as toolfound_json_to_csv, so an agent must infer which CSV tool to pick from names alone.

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 implied by the phrase 'campaign or listing-export rows', which tells the agent the intended input domain, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. Adequate but leaves selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources