Skip to main content
Glama
ms-methos

jsonfabrica-mcp-server

by ms-methos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

JsonFabrica whoami

jsonfabrica_whoami
Read-onlyIdempotent

Retrieves the tenant ID and role associated with the configured API key from the JsonFabrica gateway.

Instructions

Calls GET /v1/whoami on the JsonFabrica gateway using the configured API key. Returns { tenantId, role } for the configured JSONFABRICA_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYesRole associated with the configured API key.
tenantIdYesTenant id resolved from the configured API key.

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": {
+    "role": {
+      "description": "Role associated with the configured API key.",
+      "enum": [
+        "admin",
+        "user"
+      ],
+      "type": "string"
+    },
+    "tenantId": {
+      "description": "Tenant id resolved from the configured API key.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tenantId",
+    "role"
+  ],
+  "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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the endpoint, the auth mechanism (configured API key), and the exact return fields, which are useful beyond the annotations. No contradictions.

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 sentences, zero fluff. The endpoint and return shape are front-loaded, and every word 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?

With an output schema present, the return values are already documented. The description covers the endpoint and auth context, and annotations handle safety. Nothing essential is missing for correct invocation.

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?

There are zero parameters, so the schema is trivially covered. The description adds no param info, but none is needed. Baseline 4 for a zero-parameter tool is appropriate.

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 states the exact HTTP verb and resource (GET /v1/whoami), names the configured API key as the auth context, and specifies the exact response shape ({ tenantId, role }). It is unambiguous and clearly distinct from siblings like jsonfabrica_health.

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 description implies when to use: to retrieve the current tenant and role associated with the configured API key. There is no explicit alternative named, but given the tool is unique and self-explanatory, the context is clear. A brief 'use when you need to verify the API key' would push it to 5.

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