x402 agent toolkit: service finder, payment safety, Solana & web tools

by dev.workers.moneytools.x402-pay-precheck

YAML ↔ JSON converter

yaml_json_convert

Read-onlyIdempotent

YAML (multi-document, with line-numbered errors) to JSON, or JSON to YAML. Free: 10 calls/day; then $0.001/call via x402 (MCP params._meta["x402/payment"] or HTTP) or X-API-Key credits. [served by tools.moneytools.dev]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "yaml_json_convert"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	YAML or JSON text
`direction`	No	yaml-to-json \| json-to-yaml (auto)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower; the description adds genuinely useful context by disclosing cost and quota (10 free calls/day, $0.001/call), the two payment paths (x402 via params._meta or HTTP, X-API-Key credits), the serving host, multi-document support and line-numbered YAML errors.

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?

The conversion behavior is front-loaded in the first clause, followed by a compact billing sentence. The pricing sentence is long but earns its place given the paid x402 model; no filler beyond that.

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?

Output schema exists, both params are documented, and cost/auth/serving details are covered, so an agent has what it needs to call and pay. The main gap is guidance on direction selection and on the error format surfaced by invalid YAML.

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% and both parameters are documented there, including the 'auto' default for direction, so the baseline is 3. The description adds only the multi-document and error-detail behavior, not extra semantics for the input or direction fields.

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 conversion direction pair with concrete capabilities: 'YAML (multi-document, with line-numbered errors) to JSON, or JSON to YAML.' The formats named inherently distinguish it from csv_json_convert and xml_json_convert siblings.

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

Usage Guidelines3/5

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

Usage is implied by the format pair, but there is no explicit guidance on when to use this versus the other *_json_convert siblings or when to rely on auto-detection. The remaining space is spent on payment mechanics rather than selection guidance.

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

All x402 agent toolkit: service finder, payment safety, Solana & web tools 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?