Skip to main content
Glama

ZEAM :: Prism

by com.zeamprism
OverviewDiscussionsAdmin

Who runs ZEAM :: Prism

get_operator
Read-onlyIdempotent

Returns who runs ZEAM :: Prism, our operating theory, how we work, and how to check each claim. Free, no arguments. Example: {}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "check": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "endpoint": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "how_we_work": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "operating_theory": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "operator": {
+        "anyOf": [
+          {
+            "properties": {},
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "who": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "accepts"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "receipt"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "check": {
-    "anyOf": [
-      {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "endpoint": {
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "how_we_work": {
-    "anyOf": [
-      {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "operating_theory": {
-    "anyOf": [
-      {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "operator": {
-    "anyOf": [
-      {
-        "additionalProperties": {},
-        "properties": {},
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "who": {
-    "anyOf": [
-      {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}
  2. Changed3 schema fields changed
    • changedOutput schema / properties / check / anyOf
      Previous value: -[
-  {
-    "description": "one public thing per claim",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / operator / anyOf
      Previous value: -[
-  {
-    "additionalProperties": {},
-    "description": "legal name, jurisdiction, file number, documents, contact, support",
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / who / anyOf
      Previous value: -[
-  {
-    "description": "who runs this, in lines",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond the structured fields: the call is 'Free', which matters in a toolset containing cost-bearing operations like buy_time. It does not disclose auth requirements or rate limits, but the annotations carry most of that burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, and the cost/no-arg facts follow compactly. The 'Example: {}' fragment is mildly redundant given the empty schema, but overall the text is short and earns most of its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not enumerate return fields. For a zero-parameter informational tool with rich annotations, the definition supplies enough for an agent to call it correctly. Only the absence of explicit sibling routing keeps it from a 5.

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?

Zero parameters, so the baseline is 4. The description reinforces this with 'no arguments' and the 'Example: {}' snippet, which is consistent with the empty input schema and leaves no ambiguity about invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Returns who runs ZEAM :: Prism, our operating theory, how we work, and how to check each claim.' An agent can tell this is an informational identity/policy lookup distinct from the attest_* and audit_* siblings. It stops short of explicitly naming a sibling to contrast against, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

'Free, no arguments' implies this can be called at any time without cost or setup, which is a useful cue given paid siblings like buy_time. However, it names no alternatives and gives no explicit when-to-use or when-not-to-use condition. Usage is implied rather than stated.

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

All ZEAM :: Prism toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources