Skip to main content
Glama
Sign In

Tessryx

by io.tessryx
OverviewDiscussionsAdmin

Create datafile

create_datafile

Create a new datafile holding a JSON object. A datafile MUST be bound to a schema (schema_id) — the schema validates the JSON and generates the human editor; author or pick one with the schema tools first. Property order in json is preserved verbatim. Publish it with publish_datafile to serve it from the CDN.

Input Schema

NameRequiredDescriptionDefault
jsonYesThe JSON object this datafile holds. Property order is preserved verbatim.
slugYesURL-safe slug, optionally hierarchical.
schema_idYesId of the schema this datafile's JSON is validated against (required). The datafile's content must conform to it, and the schema generates the human editing form.
descriptionNoWhat this datafile holds.
display_nameYesHuman-readable name. Required (cannot be blank).
use_latest_schemaNoValidate against the latest (draft) schema version instead of the published one.

Output Schema

NameRequiredDescriptionDefault
jsonNo
slugYes
schema_idNo
datafile_idYes
descriptionYes
display_nameYes
content_sha256No
last_published_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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",
-  "schema_id",
-  "json"
-]New value: +[
+  "slug",
+  "display_name",
+  "schema_id",
+  "json"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description only needs to add context. It adds genuinely non-obvious behavior: schema validation is mandatory, property order in json is preserved verbatim, and creation does not itself publish to the CDN.

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?

Three short sentences, front-loaded with purpose and prerequisite, with no filler. Each sentence adds useful operational context rather than restating the title.

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?

The tool has an output schema, so return values need not be explained. The description covers the key workflow around schema binding, verbatim property ordering, and the separate publish step; it could say more about slug uniqueness or validation failure behavior, but it is nearly complete for a create tool.

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 baseline is 3. The description reinforces that schema_id is mandatory and must be authored or selected first, but most parameter meaning is already carried by the schema itself.

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 first sentence gives a specific verb and resource ("Create a new datafile") and narrows the scope to one holding a JSON object. It is clearly distinguishable from create_schema, update_datafile, and publish_datafile, which are named or implied as separate concerns.

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 explicitly states the prerequisite (a datafile MUST be bound to schema_id and schema tools should be used first) and gives the downstream step (publish_datafile to serve from CDN). It does not explicitly say when to use update_datafile instead of create_datafile, but the create-vs-publish routing is clear.

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

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