Skip to main content
Glama

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
NameRequiredDescriptionDefault
slugYesURL-safe slug, optionally hierarchical.
publishNoIf 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.
descriptionNoWhat this schema describes.
json_schemaYesThe JSON Schema body datafiles validate against; becomes version 1. Property order is preserved verbatim.
display_nameNoHuman-readable name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
versionYes
publishedYes
schema_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Explicitly states behavior: mints schema + version 1, preserves property order, defaults to unpublished draft, and publish=true publishes immediately. Also notes datafiles validate against json_schema. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured and concise despite covering multiple nuances. Two main sentences plus a parenthetical alternative. No redundant content; every sentence adds value.

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?

Complete for the context: covers purpose, usage, parameters, and alternatives. Output schema is indicated as present, so no need to describe return values. All relevant operational details are included.

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

Parameters5/5

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

Adds significant meaning beyond the schema's field descriptions: explains json_schema role, property order preservation, x-tessryx-ui hints, and publish parameter's one-step convenience. The schema already covers basic descriptions, but this enhances understanding.

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?

Clear purpose: creates a brand-new schema and its version 1. Explicitly distinguishes from create_schema_version and mentions publishing in the same step. No ambiguity.

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?

Provides strong guidance: when to use vs create_schema_version, how to publish immediately, and instructs to get_guide for UI hints. Clarifies property order importance and x-tessryx-ui needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources