Skip to main content
Glama
ms-methos

jsonfabrica-mcp-server

by ms-methos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

JsonFabrica health check

jsonfabrica_health
Read-onlyIdempotent

Check if the JsonFabrica gateway is reachable by calling its health endpoint. Verifies that JSONFABRICA_API_URL points to a valid gateway.

Instructions

Calls GET /health on the JsonFabrica gateway. No authentication required. Use this to verify JSONFABRICA_API_URL points at a reachable gateway.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesLiveness indicator, e.g. "ok".
serviceNoName of the responding service, e.g. "svc-gateway".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "service": {
+      "description": "Name of the responding service, e.g. \"svc-gateway\".",
+      "type": "string"
+    },
+    "status": {
+      "description": "Liveness indicator, e.g. \"ok\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds useful context by specifying the HTTP method and that no authentication is required.

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?

Two concise sentences fully cover purpose, method, authentication, and intended use with no filler or redundancy.

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 is complete for a health-check tool with no parameters, and since an output schema exists, return values need not be described.

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

Parameters4/5

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

With zero parameters, the baseline is 4. There are no parameter semantics to add beyond what the empty input schema already conveys.

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?

Clearly states it calls GET /health on the JsonFabrica gateway, distinguishing it from all other sibling tools that perform CRUD, generation, or usage operations.

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 says to use this tool to verify JSONFABRICA_API_URL points at a reachable gateway, giving a specific when-to-use condition.

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