Skip to main content
Glama

Hopi

by uk.co.hopi
OverviewDiscussionsAdmin

JSON to YAML converter

hopi_json_yaml_converter
Read-onlyIdempotent

Convert data between JSON and YAML in both directions. JSON to YAML parses with JSON.parse and serialises with js-yaml at two-space indent; YAML to JSON parses with js-yaml and prints with JSON.stringify. Runs on Hopi's server; nothing is stored. Source: https://hopi.co.uk/json-yaml-converter/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoDirection of conversion (default json-to-yaml)json-to-yaml
textYesThe JSON or YAML text to convert

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
outputNo
summaryYes
source_urlYesThe tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / required
      Added value: +[
+  "source_url",
+  "summary"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing implementation details: parsing with JSON.parse, serialising with js-yaml at two-space indent, printing with JSON.stringify, running on Hopi's server, and storing nothing. This gives the agent useful expectations about output formatting and privacy.

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 compact and front-loaded: purpose first, then implementation specifics, then privacy and source. Every sentence delivers useful information without repetition or padding.

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?

For a two-parameter converter with an output schema and safety annotations, the description is complete. It covers what the tool does, how it behaves in each mode, output formatting, server-side execution, privacy, and provenance. No critical operational detail is missing.

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%, so the schema already documents both parameters. The description adds some context around mode behavior, but it does not substantially expand on the meaning of the text parameter beyond what the schema provides. This aligns with 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 uses a specific verb ('convert') and resource ('data between JSON and YAML') and explicitly covers both directions. This clearly distinguishes it from one-direction sibling converters like hopi_json_to_csv and hopi_json_to_typescript.

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?

The description makes the tool's usage context clear: it handles JSON-to-YAML and YAML-to-JSON conversion. It does not explicitly name alternatives or when-not-to-use conditions, but the bidirectional scope and format-specific detail leave little ambiguity.

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

All Hopi 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