Tessryx

Create schema

create_schema

Schema authoring — create a BRAND-NEW schema (mints the schema + its version 1). json_schema is the JSON Schema body datafiles bound to this schema (by schema_id) are validated against; property order is preserved exactly — it sets the field order of the generated editor, so author it in the order you want humans to see. Media uploads, entity references, cron and colors need an x-tessryx-ui hint or they render as bare text — get_guide("schemas"). Pass publish=true to publish schema version 1 immediately (the version datafiles resolve by default), or later with publish_schema. (To add a version to a schema that already exists, use create_schema_version.)

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	URL-safe slug, optionally hierarchical.
`publish`	No	If true, immediately publish the version this call creates (the common create-then-publish in one step). Defaults to false; omit to leave the version as an unpublished draft.
`description`	No	What this schema describes.
`json_schema`	Yes	The JSON Schema body datafiles validate against; becomes version 1. Property order is preserved verbatim.
`display_name`	Yes	Human-readable name. Required (cannot be blank).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes
`version`	Yes
`published`	Yes
`schema_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

changedInput schema / properties / display_name / description

Previous value: -"Human-readable name."New value: +"Human-readable name. Required (cannot be blank)."

changedInput schema / required

Previous value: -[
-  "slug",
-  "json_schema"
-]New value: +[
+  "slug",
+  "display_name",
+  "json_schema"
+]

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds substantial non-obvious behavior: json_schema becomes version 1, property order is preserved verbatim and drives editor field order, UI hints are required for media/entity/cron/color fields, and publish=true makes the new version the one datafiles resolve by default.

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?

Dense but front-loaded: the primary purpose and the schema/version-1 outcome open the text, with the sibling alternative placed in a trailing parenthetical where it belongs. Every clause carries information, though the middle sentence packs several distinct concerns (ordering, UI hints, guide lookup) into one long run.

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?

An output schema exists so return values need no explanation, and the description covers creation semantics, optional immediate publishing, the ordering contract, and the rendering caveat for special field types. Nothing an agent needs to call this correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: json_schema's property ordering controls generated editor field order, and publish's default-resolution consequence is spelled out rather than left at 'publish the version'.

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 verb and resource ('create a BRAND-NEW schema') and clarifies the composite effect ('mints the schema + its version 1'). It explicitly distinguishes itself from the sibling create_schema_version, so an agent can route correctly without opening either schema.

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?

Names the alternative and the condition selecting it ('To add a version to a schema that already exists, use create_schema_version'), and covers the publish-now vs publish-later decision by pointing at publish_schema. It also routes to get_guide("schemas") for the x-tessryx-ui hints case.

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

All Tessryx 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?