Skip to main content
Glama

Remove Duplicate Lines API - de-duplicate and sort a list

remove_duplicate_lines
Read-onlyIdempotent

Remove duplicate lines (optionally ignoring case/spaces), drop blank lines, sort A-Z or Z-A, with counts. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/remove-duplicate-lines.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "a\nb\na\nB"
    },
    "name": "remove_duplicate_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNokeep, az or zakeep
textYesThe text
trimNoIgnore spaces at line ends
ignoreCaseNoApple = apple
removeBlankNoRemove empty lines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, and the description adds material context beyond that: server-side execution, immediate deletion of files with nothing retained, a 25 calls/day per-IP free tier, and paid x402 access with a URL. The only wrinkle is that it talks about "files" and storage while the tool takes inline text, which is mildly confusing but not a genuine conflict with readOnlyHint since the caller's data is untouched.

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?

Two sentences, both front-loaded: capabilities first, then operational facts (retention, rate limit, pricing). Nothing is repeated from the schema and no sentence is filler.

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 5-parameter, no-output-schema text tool this covers purpose, options, data handling, quotas and pricing. The phrase "with counts" is the only hint at the return shape, so an agent knows to expect counting data, but the response structure is not otherwise described — acceptable given the absence of an output schema.

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%, including defaults and an enum example for sort, so the schema carries most of the burden. The description does add a little semantic framing by grouping ignoreCase/trim as "ignoring case/spaces" and removeBlank as "drop blank lines," but it adds no syntax or edge-case detail beyond what the schema already states.

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 opens with a specific verb plus resource ("Remove duplicate lines") and immediately enumerates the exact capabilities — case/space-insensitive dedup, blank-line removal, A-Z/Z-A sorting — that map onto the tool's options. An agent can tell this apart from nearby text utilities such as list_compare or case_converter without opening the schema.

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 feature list: you would call this when you need de-duplication and/or sorting of a line list. However there is no explicit when-to-use vs. when-not guidance, no mention of which sibling to pick for plain comparison or case transformation, and no statement of input-size limits.

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