Skip to main content
Glama

ZEAM :: Prism

by com.zeamprism
OverviewDiscussionsAdmin

List the discovery documents

attest_discovery
Read-onlyIdempotent

Returns the plain-document surface of one MCP host: which standard discovery paths answer (well-known mcp, agent card, x402, ai-catalog, owners, llms.txt, openapi, server.json, robots, sitemap), and an openapi audit: operations with no security declaration, security schemes referenced but undefined, request bodies an indexer cannot read (no properties), and payment accepts that collapse on one key. It makes thirteen requests to the server named and takes as long as they take, up to 15 s each: a request not answered by then is reported timed_out, never as the server's answer. A call cut for time returns nothing. Paid, on a line: $0.000001 per millisecond. With no wallet code, ZEAM :: Pass buys the time and opens the line: a pass (https://mcp.zeamprism.com/pass) or your own wallet (https://mcp.zeamprism.com/how-to-pay). Example: {"url":"https://mcp.zeamprism.com/mcp"}

Input Schema

NameRequiredDescriptionDefault
urlYesstring — the MCP endpoint, absolute http(s) URL, e.g. https://host/mcp. Private and internal names and addresses are refused.
lineNoOptional. A line credential, for a client that cannot send the x-line header or _meta["zeam-pass/line"]: the call runs on that line's time.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "at": {
-        "anyOf": [
-          {
-            "description": "ISO time of the run",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "error": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "evidence": {
-        "anyOf": [
-          {
-            "description": "every request made, in the order sent: method, url, request headers of note, status, ms; a request that drew no answer has status 0 and its error, a redirect followed is listed in redirects, and a request still unanswered when a report was cut has unanswered: true",
-            "items": {},
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "ok": {
-        "anyOf": [
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "openapi": {
-        "anyOf": [
-          {
-            "description": "paths, operations, security per op, undefined schemes, unindexable request bodies, collapsing accepts",
-            "properties": {},
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "paths": {
-        "anyOf": [
-          {
-            "description": "each standard discovery path → status, content type, bytes",
-            "properties": {},
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sitemap_locs": {
-        "anyOf": [
-          {
-            "anyOf": [
-              {
-                "type": "number"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  },
-  {
-    "required": [
-      "accepts"
-    ],
-    "type": "object"
-  },
-  {
-    "required": [
-      "receipt"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "at": {
+        "anyOf": [
+          {
+            "description": "ISO time of the run",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "evidence": {
+        "anyOf": [
+          {
+            "description": "every request made, in the order sent: method, url, request headers of note, status, ms; a request that drew no answer has status 0 and its error; one this shelf stopped has status null and says why: timed_out with limit_ms (no answer in 15 s), too_large with limit_bytes, or canceled; a redirect followed is listed in redirects, and a request still unanswered when a report was cut has unanswered: true",
+            "items": {},
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "ok": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "openapi": {
+        "anyOf": [
+          {
+            "description": "paths, operations, security per op, undefined schemes, unindexable request bodies, collapsing accepts",
+            "properties": {},
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "paths": {
+        "anyOf": [
+          {
+            "description": "each standard discovery path → status, content type, bytes; one this shelf stopped has status null, timed_out or too_large, and the limit",
+            "properties": {},
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "sitemap_locs": {
+        "anyOf": [
+          {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "accepts"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "receipt"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, and the description adds substantial operational context: thirteen requests, 15-second per-request timeout, timed_out reporting, no return when cut for time, per-millisecond pricing, and payment/line prerequisites. Nothing contradicts the annotations.

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 and returned paths are front-loaded, followed by timeout, billing, and example details. It is dense but appropriately sized for a paid network tool with multiple behavioral caveats; a few clauses could be tightened.

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 an output schema, annotations, and 100% schema coverage, the description covers the key operational facts an agent needs: scope, timeout behavior, cost, line/pass requirement, and URL shape. No critical context appears missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the url and line parameters are already documented in the schema. The prose explains the paid-line concept and example URL, but adds little parameter-level meaning beyond what the schema provides.

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?

The description states a specific verb and resource: it returns the plain-document discovery surface of one MCP host and enumerates the paths and OpenAPI audit findings. It is clear enough to distinguish this from most siblings by output, but it never explicitly names or contrasts against sibling tools such as attest_server or audit_cluster.

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

Usage Guidelines2/5

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

The description explains what the tool returns and how billing/timeouts work, but gives no explicit guidance on when to choose it over sibling tools. There are no when-to-use, when-not-to-use, or alternative-tool statements.

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