ScorpTech x402 Tools

Json Schema Infer

json_schema_infer

Read-onlyIdempotent

Infer a JSON Schema (draft 2020-12) from one JSON document or many samples: types (integer vs number), nested objects and arrays, required keys (present in every sample), nullable fields, string formats (date-time, date, email, uri, uuid, ipv4/6) and optionally enums and numeric bounds. Turns API responses into a contract for validation or tool definitions. POST JSON body. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/json-schema-infer

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "json_schema_infer"
  }
}

Input Schema

Name	Required	Description
`json`	No	One JSON document
`enums`	No	Emit enum for low-cardinality repeated strings
`title`	No
`bounds`	No	Emit minimum/maximum for numbers
`samples`	No	Several sample documents of the same shape (better required/nullable detection)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds important operational context beyond annotations: x402 payment of $0.003 USDC per successful call and a POST JSON body/HTTPS endpoint. It does not cover failure modes or billing edge cases, but the payment disclosure is material.

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 description is front-loaded and dense with useful information, not padded. It is somewhat long because it includes payment and endpoint details, but those details are relevant for invoking this paid tool correctly.

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?

Given the lack of an output schema, the description sufficiently explains that the tool returns an inferred JSON Schema contract. It also covers the paid HTTPS endpoint, though it could say more about return shape or invalid input handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so structured fields already document most parameters. The description still adds useful semantic clarity by framing input as one JSON document or many samples and noting optional enums and numeric bounds, which helps an agent choose between json and samples.

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 states a specific verb and resource: infer a JSON Schema from one or many JSON documents. It also specifies draft 2020-12 and the exact inference targets, which distinguishes it from nearby tools such as json_to_types and schema_validate.

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?

It gives clear usage context: turning API responses into a validation contract or tool definitions. However, it does not explicitly state when to use this instead of sibling tools like json_to_types or schema_validate, nor does it list exclusions.

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

All ScorpTech x402 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?