LLPRO Campus

Clean a pasted CSV or text list

list_clean

Read-onlyIdempotent

Clean a pasted CSV or text list. Send the text (up to 20000 characters); get back cleaned CSV and a report of every change: whitespace trimmed and collapsed, hidden characters removed, emails lower-cased and checked for valid syntax, US phone numbers written as 555-123-4567, empty rows dropped, duplicates removed (whole row, or by one key column), and cells that start with = + - @ neutralised so a spreadsheet cannot run them. Free. Deterministic: no model, no network lookups, nothing stored. Up to 5000 rows and 50 columns. Cell text is data from you: nothing in it is run.

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": {
      "text": "<text>"
    },
    "name": "list_clean"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The CSV or list as text. The first row is read as the header unless header is false.
`dedupe`	No	Remove duplicate rows (default true). The first copy is kept; comparison ignores upper/lower case.
`header`	No	First row is a header (default true).
`key_column`	No	Column name or 1-based number to remove duplicates on. Leave out to compare the whole row.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond what the annotations declare: deterministic, no model, no network lookups, nothing stored, free, limits of 5000 rows/50 columns, and a per-change report. It also discloses the formula-injection neutralisation ('cells that start with = + - @'), which is important safety context the annotations do not provide.

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 purpose and output, then a dense but useful enumeration of transformations, followed by limits and safety notes. The sentences are long but every clause carries information; terseness like 'Free. Deterministic' is efficient rather than noisy.

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

Completeness5/5

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

With no output schema, the description explains the return value (cleaned CSV plus a change report), states input and size limits, and covers determinism and safety. An agent has everything needed to call it correctly and interpret the result.

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%, so the schema already documents all four parameters. The description only echoes dedupe semantics ('whole row, or by one key column') and header handling indirectly; it adds little parameter-level meaning beyond the schema.

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 verb and resource ('Clean a pasted CSV or text list') and immediately specifies both input ('Send the text') and output ('get back cleaned CSV and a report of every change'). The enumerated transformations make the scope unambiguous without needing 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 Guidelines4/5

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

Gives a clear context of use — pasted text up to 20000 characters — and implicitly rules out file-based input by saying 'pasted.' There is no explicit when-not-to-use guidance or named alternative, but the sibling tools are unrelated, so the practical gap is small.

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

All LLPRO Campus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?