Skip to main content
Glama

John's Essentials

by com.johnsessentials
OverviewDiscussionsAdmin

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 — Colour 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
NameRequiredDescriptionDefault
nameNoFile name without the extension — the extension comes from the format above. Anything over 80 characters is shortened.data
textYesThe 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.
formatNoWhat 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.

  1. Changed4 schema fields changed
    • 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."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds that this yields a 'real, downloadable file' suitable for emailing/zipping/converting, which frames persistence and downstream consumability beyond annotations — though the CSV header row and pretty-printed JSON details are largely duplicated from the schema.

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-loads verb and resource in the first sentence, then usage, then format behavior. Slightly heavy with the eight-tool em-dash list and restated CSV/JSON details, but every sentence is oriented toward routing or output shape.

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?

No output schema exists, and the description compensates by describing the artifact produced (a downloadable file in the chosen format) and its downstream uses. Format semantics are covered, so an agent has enough to invoke it correctly; only the exact return payload/URL is unspecified.

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 name, text and format are already fully documented (including the 80-char truncation and CSV/JSON behavior). The description's parameter-related content ('Point this at the earlier step...') restates the schema, so baseline 3 applies.

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 ('Write the result of an earlier step') plus the exact resource produced (a real, downloadable .txt/.csv/.json/.md file). An agent can distinguish this 'materialize output as a file' tool from save/convert/octopus_write siblings 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 Guidelines5/5

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

Explicitly says when to use it ('after any step that produces text or data rather than a file') and names the concrete upstream tools it pairs with (Colour Palette Extractor, Password Generator, Photo to Text, EXIF Viewer, Scrape Page, Word Frequency, Describe Image, PDF to Text), plus the downstream reasons (download, email, zip, convert).

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 toolsInspect
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