Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_json_schema_generator

Read-onlyIdempotent

Generate a JSON Schema (Draft-07) from a sample JSON document by analyzing structure, types, and properties. Use this to create schemas from existing data.

Instructions

JSON Schema Generator (Infer Draft-07 From Sample). Infer a JSON Schema (Draft-07, $schema fixed to http://json-schema.org/draft-07/schema#) from one sample JSON document, walking the value to emit types, properties, required, array items (oneOf for mixed element types), and optional format/pattern detection (email, date-time, uri, uuid, ipv4, ipv6) and per-property examples. Use this to draft a schema from data you already have; use webdev_json_schema_validator instead to check an existing instance against a schema you already have. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited. Returns the inferred schema as both an object and a 2-space-indented JSON string, an isValid flag, parse errors, and shape statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonYesSample JSON document to infer the schema from, as a string of raw JSON (also accepted as input).
titleNoValue placed in the generated schema top-level title field.Generated Schema
descriptionNoValue placed in the generated schema top-level description field.Schema generated from JSON data
additionalPropertiesNoSets additionalProperties on every generated object schema; false forbids unlisted keys.
detectFormatsNoDetect string format (email, date-time, uri, uuid, ipv4, ipv6) from sample values.
requireAllNoList every key in required; when false only non-null keys are required.
includeExamplesNoAdd an examples array carrying each sampled value to the generated schemas.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
isValidNoWhether the input parsed as JSON and a schema was produced.
schemaNoThe inferred JSON Schema as an object (Draft-07), or null when the input is empty or invalid.
schemaJsonNoThe inferred schema serialized as a 2-space-indented JSON string (empty string on failure).
errorsNoParse/validation errors; empty on success.
statsNoShape statistics computed from the generated schema.
Behavior5/5

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

Adds value beyond annotations by stating it runs locally, is read-only, non-destructive, contacts no external service, and is rate-limited. Also describes return format components.

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?

Slightly long but informative and front-loaded with purpose. Efficient use of words.

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 complexity (7 params, output schema present), description covers purpose, usage, behavior, and output format adequately.

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 description doesn't need to repeat parameter details. 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?

Clearly states it infers a JSON Schema (Draft-07) from a sample JSON document. Distinguishes from sibling tool webdev_json_schema_validator.

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 to use this to draft a schema from existing data and to use webdev_json_schema_validator to check an instance against a schema. Provides alternative.

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