Pulse Verity

Pulse Key Ring

pulse_key_ring

Read-onlyIdempotent

The public keys Pulse signs its price prints with, as PEM and JWK, plus the signing algorithm and the exact canonical string format — everything needed to verify a signed print yourself, OFFLINE, with no network call to Pulse. Use it to write your own verifier, or to audit what pulse_verify_print (this pack's ready-made offline checker) is checking against. Needs NO API key. Example: pulse_key_ring({}).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	Yes	How to rebuild the canonical string and verify by hand
`usage`	Yes	Points at pulse_verify_print as the ready-made offline checker
`source`	Yes	Constant: Pulse Verity Index (thepulse.markets)
`keyMode`	No	Pulse's key-storage mode, e.g. persisted
`keyless`	Yes	Always true: this tool needs no API key
`success`	No	Pulse's own success flag for this response
`activeKid`	No	The key id currently signing new prints
`algorithm`	No	Signing algorithm: ECDSA P-256, SHA-256, IEEE-P1363, base64
`canonical`	No	Canonical string template with real newlines, fields in signed order
`publicKeyJwk`	No	Active public key, JWK-encoded (kty/crv/x/y)
`publicKeyPem`	No	Active public key, PEM-encoded
`canonicalEscaped`	No	Same template with newlines rendered literally, on one line
`canonicalExample`	No	A worked canonical string example
`verificationKeys`	Yes	All keys in the ring, past and present, each usable by its kid

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activeKid": {
+      "description": "The key id currently signing new prints",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "algorithm": {
+      "description": "Signing algorithm: ECDSA P-256, SHA-256, IEEE-P1363, base64",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "canonical": {
+      "description": "Canonical string template with real newlines, fields in signed order",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "canonicalEscaped": {
+      "description": "Same template with newlines rendered literally, on one line",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "canonicalExample": {
+      "description": "A worked canonical string example",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keyMode": {
+      "description": "Pulse's key-storage mode, e.g. persisted",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keyless": {
+      "description": "Always true: this tool needs no API key",
+      "type": "boolean"
+    },
+    "note": {
+      "description": "How to rebuild the canonical string and verify by hand",
+      "type": "string"
+    },
+    "publicKeyJwk": {
+      "description": "Active public key, JWK-encoded (kty/crv/x/y)",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "publicKeyPem": {
+      "description": "Active public key, PEM-encoded",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "description": "Constant: Pulse Verity Index (thepulse.markets)",
+      "type": "string"
+    },
+    "success": {
+      "description": "Pulse's own success flag for this response",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "usage": {
+      "description": "Points at pulse_verify_print as the ready-made offline checker",
+      "type": "string"
+    },
+    "verificationKeys": {
+      "description": "All keys in the ring, past and present, each usable by its kid",
+      "items": {
+        "properties": {
+          "active": {
+            "description": "Whether this is the key currently signing",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "jwk": {
+            "description": "This key, JWK-encoded",
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "kid": {
+            "description": "Key id, matches the kid field on a signed print",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pem": {
+            "description": "This key, PEM-encoded",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "verificationKeys",
+    "note",
+    "usage",
+    "keyless",
+    "source"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedNov 7, 2026

removedInput schema / examples
```
Removed value: -[
-  {}
-]
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "activeKid": {
-      "description": "The key id currently signing new prints",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "algorithm": {
-      "description": "Signing algorithm: ECDSA P-256, SHA-256, IEEE-P1363, base64",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "canonical": {
-      "description": "Canonical string template with real newlines, fields in signed order",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "canonicalEscaped": {
-      "description": "Same template with newlines rendered literally, on one line",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "canonicalExample": {
-      "description": "A worked canonical string example",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "keyMode": {
-      "description": "Pulse's key-storage mode, e.g. persisted",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "keyless": {
-      "description": "Always true: this tool needs no API key",
-      "type": "boolean"
-    },
-    "note": {
-      "description": "How to rebuild the canonical string and verify by hand",
-      "type": "string"
-    },
-    "publicKeyJwk": {
-      "description": "Active public key, JWK-encoded (kty/crv/x/y)",
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "publicKeyPem": {
-      "description": "Active public key, PEM-encoded",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "source": {
-      "description": "Constant: Pulse Verity Index (thepulse.markets)",
-      "type": "string"
-    },
-    "success": {
-      "description": "Pulse's own success flag for this response",
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "usage": {
-      "description": "Points at pulse_verify_print as the ready-made offline checker",
-      "type": "string"
-    },
-    "verificationKeys": {
-      "description": "All keys in the ring, past and present, each usable by its kid",
-      "items": {
-        "properties": {
-          "active": {
-            "description": "Whether this is the key currently signing",
-            "type": [
-              "boolean",
-              "null"
-            ]
-          },
-          "jwk": {
-            "description": "This key, JWK-encoded",
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "kid": {
-            "description": "Key id, matches the kid field on a signed print",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "pem": {
-            "description": "This key, PEM-encoded",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "verificationKeys",
-    "note",
-    "usage",
-    "keyless",
-    "source"
-  ],
-  "type": "object"
-}New value: +null

First observedSep 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: it operates fully offline, requires no network call, and no API key, which are not derivable from annotations. It also mentions the return formats (PEM and JWK), providing additional transparency.

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 description is well-structured, front-loading the core output, then giving usage guidance and a concrete example. It is slightly longer than necessary but every sentence adds value; the example call is a nice touch. Minor redundancy in 'offline' being mentioned twice, but overall efficient.

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 zero parameters, an output schema exists (per context signals), and rich annotations, the description covers all needed context: what is returned, how to use it, why it exists, and a usage example. Nothing essential is missing for an agent to call this tool correctly.

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

Parameters5/5

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

The tool has zero parameters and schema coverage is 100% (empty schema), so the baseline is 4. The description exceeds this by showing an explicit example call 'pulse_key_ring({})', which eliminates any ambiguity about how to invoke the tool.

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 tool returns public keys, signing algorithm, and canonical string format for verifying Pulse's price prints. It distinguishes itself from sibling tools like pulse_verify_print by explicitly mentioning that it provides the raw materials for building your own verifier, making its purpose unambiguous.

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?

The description explicitly states when to use this tool: to write your own verifier or to audit what pulse_verify_print checks. It also notes that it works offline and requires no API key, giving clear context for selection among siblings.

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

All Pulse Verity tools Inspect

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.