Skip to main content
Glama
ms-methos

jsonfabrica-mcp-server

by ms-methos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get JsonFabrica tenant usage

jsonfabrica_get_usage
Read-onlyIdempotent

Retrieve usage statistics for the configured API key, returning tenant ID, total usage, and timestamp.

Instructions

Calls GET /v1/usage. Returns { tenantId, usageTotal, asOf } for the configured API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfYesISO-8601 timestamp the usage total was computed as of.
tenantIdYesTenant id the usage totals belong to.
usageTotalYesCumulative metered usage units consumed by this tenant.

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": {
+    "asOf": {
+      "description": "ISO-8601 timestamp the usage total was computed as of.",
+      "type": "string"
+    },
+    "tenantId": {
+      "description": "Tenant id the usage totals belong to.",
+      "type": "string"
+    },
+    "usageTotal": {
+      "description": "Cumulative metered usage units consumed by this tenant.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "tenantId",
+    "usageTotal",
+    "asOf"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.4

TDQS

A4.5/5.0
Behavior4/5

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

The description explicitly notes a read-only GET operation and indicates it returns data, which aligns with the readOnlyHint and idempotentHint annotations. It does not describe side effects, but none are expected for a usage retrieval endpoint.

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 a single concise sentence that includes the endpoint, return fields, and API key context, with no unnecessary wording.

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 the tool has no parameters and the description includes the return shape, endpoint, and auth context, it provides all necessary information for an agent to call it successfully.

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?

The tool has no parameters, so parameter semantics are trivially satisfied. The description does not need to explain any inputs, and the schema confirms an empty properties object.

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 HTTP method and endpoint ('Calls GET /v1/usage') and identifies the resource as tenant usage. The title and sibling context make it distinct from health, whoami, and template management tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied by the title and description: to retrieve tenant usage for the configured API key. It does not explicitly contrast with sibling tools, but the resource and endpoint are unambiguous enough for correct selection.

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