jsonfabrica-mcp-server

Overview Schema Source Related Servers Discussions Admin

Update a JsonFabrica template

jsonfabrica_update_template

Idempotent

Partially updates an existing template in place, changing only the fields you specify. Use to modify name, description, body, or tags while preserving unspecified values.

Instructions

Calls PUT /v1/templates/{templateId}. Partially updates an existing template in place: only the fields you include in the call are changed, and every field you omit is left exactly as it was — call jsonfabrica_get_template first if you need to see current values before deciding what to send. Use this only for an existing templateId; to make a new template use jsonfabrica_create_template instead (it does not modify or version the original). The change is applied immediately and in-place with no version history — there is no undo, so if you need to keep the old body/tags around, read and save them first.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	No	New template body (function-call placeholder syntax), replacing the existing one entirely. Optional; omit to leave the current body unchanged.
`name`	No	New template name. Optional; omit to leave the current name unchanged.
`tags`	No	New full set of tags, replacing (not merging with) the existing tags. Optional; omit to leave the current tags unchanged; pass an empty array to clear all tags.
`templateId`	Yes	ID of the template to update. Required.
`description`	No	New free-text description, replacing the existing one. Optional; omit to leave it unchanged.

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.

Changed6 schema fields changedSep 9, 2026

addedInput schema / properties / body / description

Added value: +"New template body (function-call placeholder syntax), replacing the existing one entirely. Optional; omit to leave the current body unchanged."

addedInput schema / properties / description / description

Added value: +"New free-text description, replacing the existing one. Optional; omit to leave it unchanged."

addedInput schema / properties / name / description

Added value: +"New template name. Optional; omit to leave the current name unchanged."

addedInput schema / properties / tags / description

Added value: +"New full set of tags, replacing (not merging with) the existing tags. Optional; omit to leave the current tags unchanged; pass an empty array to clear all tags."

addedInput schema / properties / templateId / description

Added value: +"ID of the template to update. 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.4/5.0

Behavior4/5

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

Annotations already indicate write operation (readOnlyHint=false) and idempotentHint=true. The description adds crucial behavior beyond annotations: the partial-update semantics, immediate in-place application, no version history, and no undo. It also warns to save old values if needed. No contradiction.

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?

The description is longer than necessary but each sentence carries meaningful information: method, partial update semantics, guidance to read first, sibling routing, and behavioral warnings. It is front-loaded with the key behavior and remains focused.

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?

With an output schema present, return values are covered. The description covers usage context, behavioral nuances, alternatives, and prerequisites. Nothing essential is missing for an agent to call this 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?

Schema description coverage is 100%, so every parameter is already documented in the schema. The description adds slight context about partial update semantics (omit to leave unchanged) but this is also largely captured in the schema descriptions. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('Partially updates'), a resource ('an existing template'), and the scope ('only the fields you include are changed'). It clearly distinguishes from the sibling create_template by noting it modifies an existing template rather than creating a new one.

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 instructs to use only for an existing templateId, names the alternative jsonfabrica_create_template for creation, and recommends calling jsonfabrica_get_template first to see current values. This provides clear when-to-use and when-not-to-use guidance.

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

Deploy Server