tidy-byte-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Local tools from Tidy Byte Tools. They clean messy data on this computer: repair JSON, turn notes or tables into JSON, encode or decode Base64, hash text and files, split Markdown into chunks, convert PDFs and HTML to Markdown, pull tables out of a PDF, and check web links. Most tools only read. save_chunks_jsonl, convert_to_markdown (when you set output_path), and extract_pdf_tables can write the files you ask for. check_links makes HTTP requests to the URLs you give it. No API key.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repair_json_textA | Repair broken or incomplete JSON, including output from language models. Use this when you have JSON in the conversation that may be missing quotes, have trailing commas, or be cut off. It is plain code, not an AI model: it can close missing brackets and fix common syntax issues, but it cannot invent the data you meant to write. Already-valid JSON is returned as-is, with wasValid true and repaired false. Do not use it for a file on disk (use repair_json_file for files). json_lines: if true, each non-empty line is a separate document. If false (default), the whole text is tried as one JSON value first. If that cannot be repaired and there are several lines, each line is then tried on its own. For one document, returns {"wasValid", "repaired", "value", "text"}. For several documents, returns {"count", "failed", "documents": [...]}. |
| repair_json_fileA | Read a local JSON file and repair it if it is broken or incomplete. Use this when the JSON is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Files larger than 5 MB are rejected; use the Apify version for bigger jobs. Do not use it for files that are not JSON text. path: full path to a UTF-8 text file, up to 5 MB. json_lines: if true, each non-empty line is a separate document. If false (default), the whole text is tried as one JSON value first. Returns the same object as repair_json_text. |
| shape_text_to_jsonA | Turn pasted text (key: value notes, CSV/TSV or a Markdown table) into typed JSON. Use this when you have plain-text records or a table in the conversation and need clean JSON you can trust, without guessing values yourself. It is plain code, not an AI model, so the same text always gives the same JSON and nothing is made up. Do not use it when the text is already JSON, is nested data, is app logs, or is a file on disk (use shape_file_to_json for files). format: "auto" (default) picks for you. Or force "kv" (key: value or key=value lines, a blank line starts a new record), "csv" (comma, semicolon, tab or | separated, first row is the header) or "markdown" (a | pipe | table, first row is the header). Returns {"format": , "data": }. data is a list of records for CSV and tables. For key: value text it is one object, or a list when blank lines split it into several records. Keys become lower_snake_case. Numbers become numbers, yes/no and true/false become booleans, empty or "null" becomes null. |
| shape_file_to_jsonA | Read a local text file (key: value notes, .csv, .tsv or a Markdown table) and return typed JSON. Use this when the data is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Do not use it for Excel (.xlsx), PDF or other binary files, for files that are already JSON, or for app logs. path: full path to a UTF-8 text file, up to 5 MB. format: "auto" (default) picks for you. Or force "kv" (key: value or key=value lines, a blank line starts a new record), "csv" (comma, semicolon, tab or | separated, first row is the header) or "markdown" (a | pipe | table, first row is the header). Returns {"format": , "data": }, the same as shape_text_to_json. |
| base64_convert_textA | Encode pasted text to Base64, or decode Base64 (or a data URI) back to text. Use this when you have text or a Base64 string in the conversation. It is plain code, not an AI model, so the same input always gives the same output and nothing is made up. Do not use it for a file on disk (use convert_file for files), and do not use auto on short or unusual strings if you already know the direction — pass encode or decode instead. Returns a result object. Encoded results include "action", "base64", "bytesIn", and "dataUri" plus "mime" when data_uri is true. Decoded results include "action", "bytesOut", "isText", and "text" (UTF-8 text, or null if the bytes are not text). |
| base64_convert_fileA | Read a local file and encode its bytes to Base64, or decode a Base64 text file. Use this when the data is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Files larger than 5 MB are rejected; use the Apify version for bigger jobs. For decode, the file must be UTF-8 text containing Base64 (or a data URI), not a binary file. path: full path to a file, up to 5 MB. Returns the same result object as convert_text. If the decoded bytes are not UTF-8 text, "isText" is false and "text" is null. |
| hash_textA | Hash pasted text with SHA-256, SHA-1, MD5, and optional SHA-512. Use this when you have text in the conversation and need its checksum. The text is hashed as UTF-8 bytes. It is plain code, not an AI model, so the same text always gives the same hashes. This tool does not look the hash up in a malware list or a password list. Do not use it for a file on disk (use hash_file for files). algorithms: a list from sha256, sha1, md5, sha512. Default is sha256, sha1 and md5. MD5 and SHA-1 are not safe for new security work; prefer SHA-256 or SHA-512 when you can. Returns {"ok", "bytes", "encoding": "utf-8", "hashes", and a hex field for each algorithm, plus a Base64 field when include_base64 is true}. |
| hash_fileA | Hash a local file's raw bytes with SHA-256, SHA-1, MD5, and optional SHA-512. Use this when the data is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Files larger than 5 MB are rejected; use the Apify version for bigger jobs. This tool does not look the hash up in a malware list or a password list. path: full path to a file, up to 5 MB. algorithms: a list from sha256, sha1, md5, sha512. Default is sha256, sha1 and md5. MD5 and SHA-1 are not safe for new security work; prefer SHA-256 or SHA-512 when you can. Returns {"ok", "bytes", "hashes", and a hex field for each algorithm, plus a Base64 field when include_base64 is true}. |
| chunk_markdownA | Split a Markdown file or Markdown text into chunks by heading, for search, embeddings or RAG. Use this when you need a long Markdown document (docs, notes, a README) broken into pieces that each know where they came from. A chunk never mixes two sections. Each chunk has heading_path (like ["Guide", "Install"]), anchor (the GitHub-style #link), start_line and end_line (1-based, in the file), part and parts (when a big section had to be split), chars and text. Code blocks and tables are kept whole when they fit; when they don't, each piece gets the fence or table header again. Plain code, not AI: same input, same chunks. Do not use it for PDF or Word files (convert them to Markdown first), to just see the headings (use outline_markdown), or to read one section (use get_section). Sizes are characters, not tokens. Returns {"source", "total", "start", "chunks": [...], "next_start"}. next_start is null when there are no more chunks. |
| outline_markdownA | List every heading in a Markdown file or text, with its level, path, anchor, line number and size. Use this when you want a quick map of a long document before you read or chunk it, or to find the exact heading or anchor to pass to get_section. Headings inside code blocks and YAML front matter are ignored. Both "# Title" and underlined (=== / ---) headings are found. Do not use it to get the text itself (use get_section or chunk_markdown). Returns {"source", "count", "headings": [{"level", "title", "path", "anchor", "line", "end_line", "chars"}]}. chars is the size of that heading's own text, not counting the sections under it. |
| get_sectionA | Return the text of one section of a Markdown file or text, found by heading title or anchor. Use this when you only need one part of a long document, like the "Install" section of a README, so you don't have to read the whole file. If two headings have the same title, the first one is returned and "matches" tells you how many there are; use the anchor (from outline_markdown) to pick another. Do not use it to split the whole document (use chunk_markdown). Returns {"title", "heading_path", "level", "anchor", "start_line", "end_line", "chars", "matches", "text"}. If nothing matches, the error lists the headings. |
| save_chunks_jsonlA | Split a Markdown file into chunks and save them as a JSONL file (one chunk per line). Use this when the chunks are going into a search index, vector database or another program, and you want a file instead of a long chat reply. The chunks are the same as chunk_markdown gives. It writes only the one .jsonl file and replaces it if it is already there. It never changes the Markdown file. Do not use it to look at chunks in the chat (use chunk_markdown). Returns {"output_path", "chunks", "bytes", "biggest_chunk_chars"}. |
| convert_to_markdownA | Turn a local text PDF or saved HTML file into clean Markdown. Use this when you want to read, quote, summarize or index a document as text, for example before RAG chunking or pasting into a prompt. Tables are kept as Markdown tables. Do not use it for scanned PDFs or photos (there is no OCR), for live web URLs (save the page as .html first), or when you only need the tables as CSV data (use a PDF table extractor instead). path: full path to a .pdf or .html file on this computer. tables: PDF tables. "lines" (default) finds tables with border lines, "text" also tries tables lined up by spaces, "off" gives plain text. output_path: optional. If set, the Markdown is saved there and that path is returned. An existing file at that path is replaced. If empty, nothing is written and the Markdown text is returned. Tables come back as Markdown tables. Scanned (image-only) PDF pages have no text and are skipped. |
| extract_pdf_tablesA | Pull the tables out of a local text PDF. Use this when you need the rows and columns of a table from a PDF on this computer, for example to load them into a spreadsheet, pandas or a database. Do not use it for scanned PDFs or photos (there is no OCR), for PDFs on the web (download the file first), or when you want the whole document as text (use a PDF-to-Markdown or text tool instead). path: full path to a PDF on this computer. pages: optional, like "1,3-5". Empty means all pages. strategy: "auto" (default, tries borders first, then spacing), "lines" (tables with ruled borders) or "text" (tables lined up by spacing). Try "text" if "auto" misses a table that has no border lines. output_dir: optional. If set, each table is saved there as a CSV and the file paths are returned. Files named pageN_tableM.csv that already exist there are replaced. If empty, nothing is written and the CSV text of each table is returned. Scanned (image-only) pages have no text and are skipped. Returns [] if no tables. |
| check_linksA | Check web links and follow their redirects. Use this when you have a list of URLs and need to know which ones work, which are broken (404, 500, timeouts, bad hosts) and where redirects end up, for example to clean up docs, a README, a sitemap list or bookmarks. It does not crawl a site or read page content; pass the exact links you want checked. Links that are not http or https come back with ok false and an error. urls: up to 200 http(s) links. timeout: seconds to wait for each link. Returns one result per link: {url, status, ok, final_url, redirects, error}. status is the HTTP code of the last hop (null if it could not connect). ok is true for 200-399. redirects lists each hop as "CODE url". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool targets a distinct input kind and outcome, and the descriptions explicitly cross-reference siblings with 'do not use X, use Y' guidance (text vs file variants, outline vs get_section vs chunk_markdown, convert_to_markdown vs extract_pdf_tables). The text/file pairs are the closest overlaps, but they are cleanly separated by where the data lives.
Most names follow a predictable verb_noun or resource_action pattern (repair_json_text, shape_file_to_json, hash_file, chunk_markdown, save_chunks_jsonl, check_links). The base64_convert_text / base64_convert_file pair uses a prefix-first ordering that breaks the pattern slightly, but the set remains highly readable.
Fifteen tools sits at the top of the well-scoped range and each one covers a distinct operation within a coherent local-file/plain-code utility domain. No tool looks redundant or filler.
The surface covers nearly every family symmetrically (text and file variants for repair, shaping, base64, hashing; full Markdown navigate/chunk/export lifecycle; PDF conversion and table extraction; link checking). Minor gaps exist, such as writing shaped or repaired JSON back to a file, or comparing/verifying hashes, but these are workable around.