Skip to main content
Glama
ms-methos

jsonfabrica-mcp-server

by ms-methos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a JsonFabrica sequence

jsonfabrica_get_sequence
Read-onlyIdempotent

Retrieve a named sequence record without advancing it. Use to inspect the current sequence value.

Instructions

Calls GET /v1/sequences/{name}. Returns the sequence record for a known name; use jsonfabrica_list_sequences instead if you need to discover names. Read-only — does not advance the sequence (use jsonfabrica_bump_sequence for that).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact name of the sequence to fetch, as given at creation. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSequence name.
stepNoIncrement applied per bump (ignored for "uuid").
typeYesValue kind produced on each bump.
startNoInitial value the sequence was created with.
tenantIdYesOwning tenant id.
createdAtYesISO-8601 creation timestamp.
updatedAtYesISO-8601 last-update timestamp.
currentValueYesCurrent stored counter value (unused by "uuid" sequences).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Exact name of the sequence to fetch, as given at creation. Required."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "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"
+}
  2. First observedv0.1.4

TDQS

A5/5.0
Behavior5/5

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

The description reinforces the annotation hints by explicitly noting the operation is read-only and does not advance the sequence. No side effects are hidden.

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 two concise sentences with no redundant wording. It states the endpoint, resource, and key differentiators efficiently.

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 provides enough context for correct invocation, including endpoint, parameter semantics, and side-effect behavior. The presence of an output schema covers return details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter `name` is fully described in the schema, and the description adds that it must be a known sequence name, directing discovery to the list tool. This gives complete parameter context.

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 GET /v1/sequences/{name} and returns the sequence record for a known name. It explicitly distinguishes this from list_sequences and bump_sequence, making the purpose 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?

The description gives explicit guidance: use list_sequences when discovering names and bump_sequence when advancing is needed. This makes the appropriate usage context clear.

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