Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_yaml_formatter

Read-onlyIdempotent

Format, validate, and beautify YAML documents with optional JSON conversion. Detects parse errors, mixed indentation, and trailing whitespace. Can sort keys, strip comments, or add document separators.

Instructions

YAML Formatter and Validator. Format, validate, and beautify a YAML document, with optional conversion to JSON. Pretty-prints with a chosen indent, reports parse errors with line numbers, flags mixed-indentation and trailing-whitespace warnings, and can sort keys, strip comments, add document separators, or emit equivalent JSON. Use this for YAML; use webdev_json_formatter for JSON or webdev_xml_formatter for XML. Runs locally on the text you provide (read-only, non-destructive, contacts no external service) and is rate-limited to 60 requests/minute for anonymous callers. Returns the formatted YAML, optional JSON, a validity flag, error and warning lists, and structure statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yamlYesYAML document to process. Must not be blank.
formatNoRe-serialize (pretty-print) the parsed data; when false the original text is returned unchanged.
validateNoParse the input to determine validity and collect warnings.
indentSizeNoSpaces per indent level for the formatted output (UI offers 2, 4, or 8).
arrayStyleNoSequence rendering: block (one item per line) or inline (flow style).block
objectStyleNoMapping rendering: block (one key per line) or inline (flow style).block
convertToJsonNoAlso emit the data as 2-space-indented JSON in the json field.
sortKeysNoRecursively sort mapping keys alphabetically before output.
removeCommentsNoDrop lines that are YAML comments from the formatted output.
addDocumentSeparatorNoWrap output with a leading start marker and a trailing end marker.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalNoThe submitted YAML, echoed back.
formattedNoThe formatted YAML (or original text when format is false or parsing failed).
jsonNoEquivalent JSON when convertToJson is true, otherwise an empty string.
isValidNoWhether the input parsed as valid YAML.
errorsNoParse error messages (empty when valid).
warningsNoNon-fatal lint warnings with line numbers (mixed indentation, trailing whitespace).
statsNoStructure and size metrics for the document.
Behavior5/5

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

Description adds beyond annotations: 'Runs locally... read-only, non-destructive, contacts no external service' and 'rate-limited to 60 requests/minute'. No contradiction with readOnlyHint, destructiveHint, or idempotentHint.

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?

Description is concise and well-structured: starts with core purpose, lists features, then usage guidance and technical details. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given high parameter count, full schema coverage, and rich annotations, the description completes the picture by stating return values (formatted YAML, optional JSON, validity flag, errors, warnings, statistics) and behavioral constraints (local, rate-limited).

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 coverage is 100% with detailed parameter descriptions. Description provides a high-level overview of features (e.g., sorting keys, stripping comments) but does not add significant information beyond the schema for individual parameters. Baseline 3 is appropriate.

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?

Description clearly states the tool formats, validates, and beautifies YAML, with optional JSON conversion. It explicitly distinguishes from siblings: 'Use this for YAML; use webdev_json_formatter for JSON or webdev_xml_formatter for XML.'

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 this tool versus alternatives for JSON and XML. Also describes local, read-only execution and rate limits, providing clear context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server