MoneyTools x402 agent toolkit

JSON Schema validator

json_schema_validate

Read-onlyIdempotent

Validate JSON data against a JSON Schema (draft 4, 7, 2019-09, 2020-12) and get precise error paths. Use it to check tool outputs or API payloads. 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": {
      "schema": "<schema>",
      "data": "<data>"
    },
    "name": "json_schema_validate"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	JSON value to validate
`draft`	No	4 \| 7 \| 2019-09 \| 2020-12 (default)
`schema`	Yes	JSON Schema

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedInput schema / properties / data / examples

Added value: +[
+  {
+    "name": "gas",
+    "price": 0.001
+  }
+]

addedInput schema / properties / schema / examples

Added value: +[
+  {
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "name",
+      "price"
+    ],
+    "type": "object"
+  }
+]

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and openWorld, so the description's real contribution is the commercial constraint: a 10 calls/day free tier, then $0.001/call via x402 (_meta["x402/payment"]) or X-API-Key credits. That is exactly the kind of cost/auth behavior an agent needs before invoking, though nothing is said about payload size limits or latency.

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?

Purpose and capability come first, then usage, then pricing, which is the right ordering. The payment sentence is dense with x402/X-API-Key detail but each element is actionable; the '[served by tools.moneytools.dev]' tag is marginal.

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?

With an output schema present, the description needn't explain return values, and all three parameters are schema-documented. The remaining need for a caller — cost and auth path — is covered. Minor gaps: no stated input size limits and no guidance on which draft to pick when the caller is unsure.

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 description coverage is 100%, so the schema already documents all three parameters. The description only echoes the draft values ('draft 4, 7, 2019-09, 2020-12') that the schema's own draft field already lists, adding no new meaning. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Validate JSON data against a JSON Schema') and adds supported drafts plus the output trait ('precise error paths'). It does not explicitly distinguish itself from nearby siblings such as json_repair or json_format, so it stops short of a 5.

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?

'Use it to check tool outputs or API payloads' gives a usage context, which is more than nothing. There are no exclusions, no prerequisites, and no named alternative (e.g., when to repair vs. validate), so routing still requires inference.

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

All MoneyTools x402 agent toolkit 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?