jsonfabrica-mcp-server

Overview Schema Source Related Servers Discussions Admin

List JsonFabrica templates

jsonfabrica_list_templates

Read-onlyIdempotent

List and filter available JSON templates by name, tags, or status to find the right template for your data generation needs.

Instructions

Calls GET /v1/templates. Returns a page of templates matching optional name/tags/status filters ({ items, nextCursor }). Use this to discover or search templates when you don't already know the templateId; if you already have the id, call jsonfabrica_get_template directly instead — it is cheaper and returns the full record. This is read-only and has no side effects. Pass status: "archived" to see templates previously removed with jsonfabrica_delete_template, since the default active filter excludes them.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Filters to templates whose `name` contains this text — a case-insensitive substring match, not an exact match. Optional; omit to match templates of any name.
`tags`	No	Comma-separated list of tags, e.g. "orders,email". AND-match: a template must contain every listed tag to be included (not "any of"). Optional; omit to ignore tags entirely.
`limit`	No	Maximum number of templates to return in this page. Optional; defaults to 20 when omitted. Values <= 0 or > 100 are not clamped — the request is rejected with a 400 validation error.
`cursor`	No	Opaque pagination cursor taken verbatim from a previous response's `nextCursor`. Optional; omit to fetch the first page.
`status`	No	`active` returns only non-deleted templates, `archived` returns only soft-deleted ones. Optional; defaults to `active` when omitted (archived templates are excluded unless requested).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	Page of matching templates.
`nextCursor`	No	Pass to `cursor` on the next call to fetch the following page; absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 9, 2026

addedInput schema / properties / cursor / description

Added value: +"Opaque pagination cursor taken verbatim from a previous response's `nextCursor`. Optional; omit to fetch the first page."

addedInput schema / properties / limit / description

Added value: +"Maximum number of templates to return in this page. Optional; defaults to 20 when omitted. Values <= 0 or > 100 are not clamped — the request is rejected with a 400 validation error."

addedInput schema / properties / name / description

Added value: +"Filters to templates whose `name` contains this text — a case-insensitive substring match, not an exact match. Optional; omit to match templates of any name."

addedInput schema / properties / status / description

Added value: +"`active` returns only non-deleted templates, `archived` returns only soft-deleted ones. Optional; defaults to `active` when omitted (archived templates are excluded unless requested)."

changedInput schema / properties / tags / description

Previous value: -"Comma-separated list of tags, e.g. \"orders,email\"."New value: +"Comma-separated list of tags, e.g. \"orders,email\". AND-match: a template must contain every listed tag to be included (not \"any of\"). Optional; omit to ignore tags entirely."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "description": "Page of matching templates.",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "description": "Pass to `cursor` on the next call to fetch the following page; absent on the last page.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedv0.1.4Sep 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reaffirms 'read-only and has no side effects' (consistent, not contradictory). It adds valuable behavior beyond annotations: default active filter, pagination via nextCursor, and that archived templates are excluded unless requested. This context enriches the agent's understanding without relying solely on structured hints.

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 compact and front-loaded: endpoint, return shape, then usage guidance. Every sentence earns its place, covering filters, alternative, read-only nature, and archived use case without redundancy. Well-structured and efficient.

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?

For a list tool with 5 parameters and an output schema, the description covers discovery, pagination, filter semantics, the read-only nature, and the alternative tool. Nothing an agent needs to call it correctly is missing. The presence of an output schema means return values need not be explained further.

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 coverage is 100%—every parameter has a detailed description, so the schema already carries the heavy lifting. The description adds a usage example (pass status archived) but does not introduce new parameter meaning beyond what the schema provides. Baseline 3 is appropriate given full schema coverage.

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 HTTP verb, resource, and return shape, and explicitly differentiates from jsonfabrica_get_template by saying it is for discovery when you don't know the templateId. The purpose is unambiguous and distinguishable from siblings.

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 when to use this tool (discover/search when templateId unknown) and when to use the alternative (jsonfabrica_get_template if you already have the id), noting it is cheaper. Also gives a concrete use case for the archived status filter. Provides clear routing guidance.

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

Deploy Server