jsonfabrica-mcp-server

Overview Schema Source Related Servers Discussions Admin

Delete a JsonFabrica template

jsonfabrica_delete_template

DestructiveIdempotent

Archive a template by setting its status to 'archived' without erasing it, so it stops appearing in normal listings while remaining accessible for reads and generation.

Instructions

Calls DELETE /v1/templates/{templateId}. This is a soft delete: the template's status is set to "archived" (it is not erased from storage), and the call returns the resulting archived template record. Archived templates are excluded from jsonfabrica_list_templates by default — pass status: "archived" there to find them again — and both jsonfabrica_get_template and jsonfabrica_generate_from_template still work against the id afterwards, since archiving does not block reads or generation. Use this when a template should stop showing up in normal listings; there is currently no tool to restore an archived template back to active.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`templateId`	Yes	ID of the template to delete. Required.

Output Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	Template body containing function-call placeholders.
`name`	Yes	Template name.
`tags`	No	Tags stored on the template.
`status`	Yes	"active" unless soft-deleted via jsonfabrica_delete_template.
`astCache`	No	Server-internal parsed-body cache; opaque to callers.
`tenantId`	Yes	Owning tenant id.
`warnings`	No	Non-fatal validation warnings, if any.
`createdAt`	Yes	ISO-8601 creation timestamp.
`updatedAt`	Yes	ISO-8601 last-update timestamp.
`validated`	No	Whether the body passed static template validation.
`templateId`	Yes	Server-assigned template id.
`description`	No	Free-text description, if any was stored.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 9, 2026

addedInput schema / properties / templateId / description

Added value: +"ID of the template to delete. Required."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "astCache": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Server-internal parsed-body cache; opaque to callers."
+    },
+    "body": {
+      "description": "Template body containing function-call placeholders.",
+      "type": "string"
+    },
+    "createdAt": {
+      "description": "ISO-8601 creation timestamp.",
+      "type": "string"
+    },
+    "description": {
+      "description": "Free-text description, if any was stored.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Template name.",
+      "type": "string"
+    },
+    "status": {
+      "description": "\"active\" unless soft-deleted via jsonfabrica_delete_template.",
+      "enum": [
+        "active",
+        "archived"
+      ],
+      "type": "string"
+    },
+    "tags": {
+      "description": "Tags stored on the template.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "templateId": {
+      "description": "Server-assigned template id.",
+      "type": "string"
+    },
+    "tenantId": {
+      "description": "Owning tenant id.",
+      "type": "string"
+    },
+    "updatedAt": {
+      "description": "ISO-8601 last-update timestamp.",
+      "type": "string"
+    },
+    "validated": {
+      "description": "Whether the body passed static template validation.",
+      "type": "boolean"
+    },
+    "warnings": {
+      "description": "Non-fatal validation warnings, if any.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "templateId",
+    "tenantId",
+    "name",
+    "body",
+    "status",
+    "createdAt",
+    "updatedAt"
+  ],
+  "type": "object"
+}

First observedv0.1.4Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description transparently explains the soft-delete behavior, that get and generate still work, that list excludes archived templates by default, and that the call returns the archived record. This is fully consistent with destructiveHint and idempotentHint.

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?

The description is detailed but every sentence contributes meaningful behavior, use-case guidance, and caveats. It is well-structured and avoids redundant filler.

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?

The description fully covers the operation's side effects, return value, effect on sibling operations, intended use case, and the lack of a restore path. This gives an agent enough context to decide when and how to invoke the tool correctly.

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?

The single parameter templateId is described in both the schema and the description as the ID of the template to delete and required. Since schema coverage is 100% and the description adds no additional parameter-level detail, the baseline score applies.

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 clearly states the tool calls DELETE /v1/templates/{templateId} and defines the operation as a soft delete that sets status to 'archived'. It distinguishes this from a hard deletion and explicitly differentiates it from related template tools.

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?

It provides explicit guidance on when to use the tool: when a template should stop appearing in normal listings. It also warns that no tool currently restores an archived template to active, preventing misuse.

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

Deploy Server