Tanod MCP server

utilpeek: sort, dedupe and clean up lines of text

text_lines

Read-onlyIdempotent

Transform lines of text by trimming, deduping, sorting, reversing, shuffling, or numbering them; optionally count unique lines.

Instructions

utilpeek: Sort, dedupe, trim, shuffle or number the lines of a text. For find and replace use text_replace. Returns the text's lines transformed by operations in order: trim, remove_empty, dedupe (keeps the first), sort (lexical, natural or length; stable), reverse, shuffle (seeded, repeatable) and number; optionally the most frequent lines with counts. At most 200,000 lines. Typically under 0.3 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`seed`	No	Shuffle seed: same seed, same order.
`text`	Yes	The text (at most 200,000 characters).
`top_n`	No	With count_unique: how many of the most frequent lines to return (1-1000, default 100).
`sort_mode`	No	For sort: lexical (default, by character), natural (numbers by value: item 9 before item 10) or length (shortest first).	lexical
`descending`	No	For sort: largest first (default false: ascending).
`operations`	Yes	Applied in order: trim, remove_empty, dedupe, sort, reverse, shuffle, number.
`count_unique`	No	Also return the most frequent lines with counts.
`number_start`	No	For number: the first line's number (-1,000,000 to 1,000,000; default 1).
`case_insensitive`	No	dedupe / sort / count compare casefolded lines.
`number_separator`	No	For number: text between the number and the line (at most 10 characters; default ". ").	.

Output Schema

TableJSON Schema

Name	Required	Description
`top`	No
`seed`	No
`text`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`source`	No
`removed`	No
`lines_in`	No
`lines_out`	No
`operations`	No
`unique_lines`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, and the description adds genuinely new behavioral context: deterministic seeded shuffle, stable sort, dedupe keeps the first occurrence, a 200,000-line ceiling, ~0.3 s latency, price, a 10-calls/IP/day free quota, and an explicit statement that submitted text is never logged or stored. These are exactly the rate-limit, cost, and data-handling details that annotations do not carry.

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, then exclusion, then mechanics, then constraints/pricing in a single dense paragraph with little waste. The 'utilpeek:' prefix and pricing/free-tier boilerplate are mildly extraneous for tool selection but still informative.

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?

An output schema exists so return values need no explanation, and the description covers limits, latency, operation ordering, and determinism. One small gap: it says 'At most 200,000 lines' while the text parameter caps at 200,000 characters, and it does not describe behavior on over-limit input.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by restating the execution order of operations and specifying that dedupe keeps the first occurrence and that shuffle is seeded/repeatable, details the enum entries alone do not convey.

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 set (sort, dedupe, trim, shuffle, number) and resource (lines of text), and explicitly disambiguates from the sibling text_replace for find/replace. An agent can tell it apart from text_stats or diff_text 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 Guidelines4/5

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

Gives an explicit exclusion and alternative: 'For find and replace use text_replace.' However, it does not route the agent away from other overlapping siblings such as text_frequency (despite offering 'most frequent lines with counts') or text_stats, so selection guidance is clear but not exhaustive.

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

Deploy Server