John's Essentials

convert_text

Text Converter — Convert text/data formats: Markdown↔HTML, CSV↔JSON, JSON↔XML/YAML, Base64 and URL encode/decode. Takes 'text' + 'from' + 'to' — there is no 'conversion_type' field. [category: convert]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes	What you want back. Must differ from the source. For a Base64 or URL encode/decode, leave this on the format you want the result read as — do NOT pick plain text, which currently returns the input untouched.	html
`from`	Yes	What the text is now — or the encoding job to run (Base64 / URL encode and decode ride in this field).	md
`text`	Yes	The text/data to convert. Field name is 'text' — not 'content'.

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedSep 11, 2026

changedInput schema / properties / to / description

Previous value: -"What you want back. Must differ from the source. Supported pairs: Markdown↔HTML, CSV→JSON/XML, JSON↔CSV, JSON↔XML, JSON↔YAML, XML→JSON, and anything→plain text."New value: +"What you want back. Must differ from the source. For a Base64 or URL encode/decode, leave this on the format you want the result read as — do NOT pick plain text, which currently returns the input untouched."

Changed6 schema fields changedSep 11, 2026

addedInput schema / properties / from / default
```
Added value: +"md"
```

changedInput schema / properties / from / description

Previous value: -"Source format or operation: md, html, csv, json, xml, yaml — or base64_encode, base64_decode, url_encode, url_decode (the operation rides in 'from')."New value: +"What the text is now — or the encoding job to run (Base64 / URL encode and decode ride in this field)."

addedInput schema / properties / from / enum

Added value: +[
+  "md",
+  "html",
+  "csv",
+  "json",
+  "xml",
+  "yaml",
+  "base64_encode",
+  "base64_decode",
+  "url_encode",
+  "url_decode"
+]

addedInput schema / properties / to / default
```
Added value: +"html"
```

changedInput schema / properties / to / description

Previous value: -"Target format: html, md, json, csv, xml, yaml, txt. Must differ from 'from'. Supported pairs: md↔html, csv→json/xml, json↔csv, json↔xml, json↔yaml, xml→json, any→txt; for encode/decode operations set to='txt'."New value: +"What you want back. Must differ from the source. Supported pairs: Markdown↔HTML, CSV→JSON/XML, JSON↔CSV, JSON↔XML, JSON↔YAML, XML→JSON, and anything→plain text."

addedInput schema / properties / to / enum

Added value: +[
+  "html",
+  "md",
+  "json",
+  "csv",
+  "xml",
+  "yaml",
+  "txt"
+]

First observedSep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds behavioral notes beyond the annotations: it warns that the 'to' field must not be set to 'plain text' for Base64/URL operations (which would return input unchanged), and it explicitly states there is no 'conversion_type' field. These details help agents avoid common mistakes. The annotations are minimal (readOnlyHint=false, destructiveHint=false) and the description supplements them well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, information-dense sentence followed by a parenthetical note. It front-loads the core purpose and immediately states the required parameters, then adds a caveat. Every sentence contributes meaning without redundancy, making it concise and well-structured.

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?

The tool has no output schema, so the description must convey return expectations, and it does so implicitly (converted text) but does not specify the response format or error handling. However, for a straightforward converter, the key behavioral quirks are covered. The description is adequate for an agent to call the tool correctly, though it could mention output format or failure modes.

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 parameters are documented, but the description adds value by clarifying the 'from' and 'to' fields' special behavior for Base64/URL encoding, and by correcting a potential misconception about a 'conversion_type' field. This goes beyond the schema's own descriptions, which are already detailed, so the description earns a slight bonus over the baseline 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 explicitly states it converts text/data formats and lists the specific conversions (Markdown↔HTML, CSV↔JSON, JSON↔XML/YAML, Base64/URL encode-decode). The verb 'convert' plus the resource 'text/data' and the format list make the purpose unambiguous. It also clarifies the exact parameter names, distinguishing it from potential sibling converters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternative converters like convert_data or convert_file. It does not mention exclusions or conditions that would route an agent to a sibling. The only implicit hint is the format list, but no explicit 'use when' or 'don't use when' guidance is given.

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?