Convert a JSON object to clean, human-readable YAML. Handles nested objects, arrays, multiline strings, and special characters. No external dependencies.
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | The JSON to convert to YAML — a JSON string, or the value itself. | |
| indent | No | Indentation size in spaces (default: 2) |
| Name | Required | Description | Default |
|---|---|---|---|
| yaml | No | ||
| lines | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "input": {
+ "a": "x: y",
+ "c": null,
+ "d": "yes",
+ "e": "0123"
+ }
+ }
+]Input schema / properties / input / descriptionPrevious value: -"JSON string to convert to YAML"New value: +"The JSON to convert to YAML — a JSON string, or the value itself."Input schema / properties / input / typePrevious value: -"string"New value: +[
+ "string",
+ "object",
+ "array"
+]Output schema / propertiesAdded value: +{
+ "lines": {
+ "type": "number"
+ },
+ "yaml": {}
+}Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real capability scope beyond that — nested objects, arrays, multiline strings, special characters — which tells the agent what input shapes will round-trip cleanly. It omits behavior on malformed JSON, which is the main remaining gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core action, with no repetition of the schema. 'No external dependencies' is the weakest line — mildly useful operationally but not decision-relevant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, so return values need no explanation, and parameters are fully covered by the schema. The description supplies the capability scope an agent needs for a two-parameter converter; only error-handling behavior is unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both the 'input' (string, object, or array) and 'indent' (default 2) parameters are fully documented in structured fields, and an example is included. The description adds no further semantics, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Convert a JSON object to ... YAML') with an unambiguous direction, which implicitly distinguishes it from the inverse sibling yaml_to_json. It does not explicitly name the sibling, but no agent could confuse the two.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the tool's nature as a simple format converter; there is no statement of when to prefer it over alternatives such as format_json or yaml_to_json, nor any preconditions. For a self-evident utility this is adequate but leaves routing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.