Skip to main content
Glama
ms-methos

jsonfabrica-mcp-server

by ms-methos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List JsonFabrica sequences

jsonfabrica_list_sequences
Read-onlyIdempotent

List sequences to discover their names when you don't know one. Returns a paginated page with items and nextCursor for browsing.

Instructions

Calls GET /v1/sequences. Returns a page of sequences ({ items, nextCursor }). Use this to discover sequence names when you don't already know one; if you know the exact name, call jsonfabrica_get_sequence directly instead. Read-only, no side effects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of sequences 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.
cursorNoOpaque pagination cursor from a previous response's `nextCursor`. Optional; omit to fetch the first page. Not a page number or offset you construct yourself.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesPage of matching sequences.
nextCursorNoPass to `cursor` on the next call; absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque pagination cursor from a previous response's `nextCursor`. Optional; omit to fetch the first page. Not a page number or offset you construct yourself."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of sequences 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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "description": "Page of matching sequences.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "createdAt": {
+            "description": "ISO-8601 creation timestamp.",
+            "type": "string"
+          },
+          "currentValue": {
+            "description": "Current stored counter value (unused by \"uuid\" sequences).",
+            "type": "number"
+          },
+          "name": {
+            "description": "Sequence name.",
+            "type": "string"
+          },
+          "start": {
+            "description": "Initial value the sequence was created with.",
+            "type": "number"
+          },
+          "step": {
+            "description": "Increment applied per bump (ignored for \"uuid\").",
+            "type": "number"
+          },
+          "tenantId": {
+            "description": "Owning tenant id.",
+            "type": "string"
+          },
+          "type": {
+            "description": "Value kind produced on each bump.",
+            "enum": [
+              "number",
+              "string",
+              "uuid"
+            ],
+            "type": "string"
+          },
+          "updatedAt": {
+            "description": "ISO-8601 last-update timestamp.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tenantId",
+          "name",
+          "type",
+          "currentValue",
+          "createdAt",
+          "updatedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "description": "Pass to `cursor` on the next call; absent on the last page.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.4

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the return shape `{ items, nextCursor }` and repeats 'Read-only, no side effects,' but adds little beyond what annotations and schema already convey. It does not introduce any contradiction.

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 three sentences, front-loaded with the HTTP call and return shape, followed by concise usage guidance and a safety note. No filler or redundant details—every sentence earns its place.

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?

Given an output schema exists (noted in context), the description need not detail the full return structure. It covers the discovery use case, pagination behavior, and explicitly states the alternative tool. For a simple read-only list operation, nothing essential is missing.

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%, with both limit and cursor having detailed descriptions. The description's mention of cursor from a previous response's nextCursor is already covered in the schema, so it adds no new meaning beyond what the schema provides. Baseline of 3 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?

Description states the specific HTTP call (GET /v1/sequences) and the return shape (a page of sequences with items and nextCursor). It also differentiates from the sibling jsonfabrica_get_sequence by clarifying when to use each, so the purpose is unambiguous.

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 this tool for discovery when the sequence name is unknown, and directs to jsonfabrica_get_sequence when the exact name is known. This leaves no ambiguity about when to choose this over the sibling.

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

Deploy Server

Other Tools