John's Essentials

data_to_file

Save as File — Write the result of an earlier step to a real, downloadable file: .txt, .csv, .json or .md. Use after any step that produces text or data rather than a file — Color Palette Extractor, Password Generator, Photo to Text (OCR), EXIF Viewer, Scrape Page, Word Frequency, Describe Image, PDF to Text — so the result can be downloaded, emailed, zipped or converted. A list of values saved as CSV becomes a spreadsheet with a header row. [category: utility]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	File name without the extension — the extension comes from the format above. Anything over 80 characters is shortened.	data
`text`	Yes	The result to save. Point this at the earlier step whose text or data you want in the file — the colour palette, the password, the extracted text.
`format`	No	What kind of file to write. csv turns a list of values into a spreadsheet — a header row and one row per value — and anything it cannot tabulate becomes a single column. json is pretty-printed, and data that is not valid JSON is saved as plain text instead.	txt

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / text / x-ui
```
Added value: +{
+  "multiline": true
+}
```

Changed4 schema fields changedSep 11, 2026

changedInput schema / properties / format / description

Previous value: -"What kind of file to write. csv turns a list of values into a spreadsheet; json is pretty-printed."New value: +"What kind of file to write. csv turns a list of values into a spreadsheet — a header row and one row per value — and anything it cannot tabulate becomes a single column. json is pretty-printed, and data that is not valid JSON is saved as plain text instead."

addedInput schema / properties / name / default
```
Added value: +"data"
```

changedInput schema / properties / name / description

Previous value: -"Optional file name without the extension (default: data)."New value: +"File name without the extension — the extension comes from the format above. Anything over 80 characters is shortened."

changedInput schema / properties / text / description

Previous value: -"The data to save — normally an earlier step's output, e.g. {{step_1.text}} or {{step_1.palette}}."New value: +"The result to save. Point this at the earlier step whose text or data you want in the file — the colour palette, the password, the extracted text."

AddedSep 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses that the tool writes a file, which goes beyond the basic annotations (readOnlyHint=false, destructiveHint=false). It also mentions the file is downloadable and can be emailed/zipped/converted. The CSV and JSON behavior details are already in the parameter schema, so the description adds some but not extensive behavioral context. No contradiction with annotations.

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?

The description is well-structured with a clear headline and logical flow. The list of example upstream tools adds length but is directly useful for routing agents. It is not overly verbose, and every sentence contributes to understanding the tool's role.

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?

Given the tool's simplicity (3 params, 1 required, no output schema), the description covers the essential use case, when to use it, and the output nature (a downloadable file). It does not explain what happens if the file already exists (likely overwrites) but that is not critical. The schema fills in parameter details, so overall the description is complete enough.

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%, and the tool description largely repeats what the schema already explains about the parameters (CSV tabulation, JSON pretty-printing, name length limit). It does not add significant new meaning beyond the schema, so it stays at the baseline of 3.

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 states a precise action ('Write the result of an earlier step to a real, downloadable file') with supported formats (.txt, .csv, .json, .md). It clearly differentiates from sibling tools by focusing on saving in-memory results to files, not converting, analyzing, or generating. Specific examples of upstream tools (Color Palette Extractor, Password Generator, etc.) further clarify its role.

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?

Explicitly says 'Use after any step that produces text or data rather than a file' and lists many such tools, providing strong when-to-use guidance. It does not explicitly name alternative tools for when not to use it (e.g., when you already have a file to convert), but the purpose is distinct enough that this is not a major gap.

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

All John's Essentials 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?