Skip to main content
Glama
Sign In

Pulse Verity

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Pulse Settlement Print

pulse_settlement_print
Read-onlyIdempotent

The signed index print Pulse RECORDED nearest a past moment — the tool for settling a contract, pricing an option at expiry, or reconstructing what an asset was worth at a specific timestamp. Returns the observation with its original signature intact — verify it offline with pulse_verify_print, no network call — plus delta_ms, the distance between the time you asked for and the print actually returned; it is the nearest recorded print, never a price synthesised at your exact instant. Accepts ISO-8601 or epoch milliseconds. Requires a Pulse API key via _apiKey. Example: pulse_settlement_print({ symbol: "BTC", at: "2026-09-16T21:41:46.000Z" }).

Input Schema

NameRequiredDescriptionDefault
atYesThe moment to price, as ISO-8601 (2026-09-16T21:41:46.000Z) or epoch milliseconds.
symbolYesAsset ticker, e.g. BTC.
_apiKeyNoPulse Verity API key. Free and self-serve at https://thepulse.markets/developers (60 req/min, 25,000/month, no card).

Output Schema

NameRequiredDescriptionDefault
printYesThe signed print Pulse recorded nearest the requested time
sourceYesConstant: Pulse Verity Index (thepulse.markets)
delta_msNoDistance in ms between requested_at and the print returned
delta_noteNoExplains delta_ms — the returned print is the NEAREST observation to requested_at, not necessarily AT it.
requested_atYesThe `at` argument as supplied by the caller

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "at": "2026-09-16T21:46:04.588Z",
+    "symbol": "BTC"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "delta_ms": {
+      "description": "Distance in ms between requested_at and the print returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "delta_note": {
+      "description": "Explains delta_ms — the returned print is the NEAREST observation to requested_at, not necessarily AT it.",
+      "type": "string"
+    },
+    "print": {
+      "description": "The signed print Pulse recorded nearest the requested time",
+      "properties": {
+        "at": {
+          "description": "Recorded timestamp, 4th field of the signed canonical string",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "deltaMs": {
+          "description": "Milliseconds between the requested time and this print",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "grade": {
+          "description": "consensus/blended/indicative, 5th field of the signed canonical string",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "grade_note": {
+          "description": "Plain-English meaning of grade and whether it is settleable",
+          "type": "string"
+        },
+        "kid": {
+          "description": "Key id selecting which public key verifies the signature",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "price": {
+          "description": "Price as a float; priceText is what was actually signed",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "priceText": {
+          "description": "Price exactly as served, 3rd field of the signed canonical string",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "settleable": {
+          "description": "True only for consensus/blended grades",
+          "type": "boolean"
+        },
+        "sig": {
+          "description": "Signing scheme tag, 1st field of the canonical string (pulse-index-v1)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "signature": {
+          "description": "Base64 ECDSA P-256 signature over the canonical string",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Asset ticker, 2nd field of the signed canonical string",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "requested_at": {
+      "description": "The `at` argument as supplied by the caller",
+      "type": "string"
+    },
+    "source": {
+      "description": "Constant: Pulse Verity Index (thepulse.markets)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "print",
+    "requested_at",
+    "source"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "at": "2026-09-16T21:46:04.588Z",
-    "symbol": "BTC"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "delta_ms": {
-      "description": "Distance in ms between requested_at and the print returned",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "delta_note": {
-      "description": "Explains delta_ms — the returned print is the NEAREST observation to requested_at, not necessarily AT it.",
-      "type": "string"
-    },
-    "print": {
-      "description": "The signed print Pulse recorded nearest the requested time",
-      "properties": {
-        "at": {
-          "description": "Recorded timestamp, 4th field of the signed canonical string",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "deltaMs": {
-          "description": "Milliseconds between the requested time and this print",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "grade": {
-          "description": "consensus/blended/indicative, 5th field of the signed canonical string",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "grade_note": {
-          "description": "Plain-English meaning of grade and whether it is settleable",
-          "type": "string"
-        },
-        "kid": {
-          "description": "Key id selecting which public key verifies the signature",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "price": {
-          "description": "Price as a float; priceText is what was actually signed",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "priceText": {
-          "description": "Price exactly as served, 3rd field of the signed canonical string",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "settleable": {
-          "description": "True only for consensus/blended grades",
-          "type": "boolean"
-        },
-        "sig": {
-          "description": "Signing scheme tag, 1st field of the canonical string (pulse-index-v1)",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "signature": {
-          "description": "Base64 ECDSA P-256 signature over the canonical string",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "description": "Asset ticker, 2nd field of the signed canonical string",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "requested_at": {
-      "description": "The `at` argument as supplied by the caller",
-      "type": "string"
-    },
-    "source": {
-      "description": "Constant: Pulse Verity Index (thepulse.markets)",
-      "type": "string"
-    }
-  },
-  "required": [
-    "print",
-    "requested_at",
-    "source"
-  ],
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Discloses that the returned observation keeps its original signature and can be verified offline with pulse_verify_print, that it returns delta_ms as a distance metric, and that the print is the nearest recorded one rather than an interpolated price. These behaviors go well beyond the readOnly/idempotent annotations and give the agent an accurate mental model.

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 front-loaded with purpose and packed with behavioral details, an example, and auth requirements. It is somewhat run-on, but every clause adds value and no irrelevant material appears.

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 available, return-value documentation is handled elsewhere. The description covers use cases, nearest-print semantics, timestamp formats, offline verification workflow, authentication, and a concrete call example, so an agent has everything needed to invoke it correctly.

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 coverage is 100%, with clear descriptions for at, symbol, and _apiKey. The description reinforces the ISO-8601/epoch format and the _apiKey requirement, but adds little parameter-specific meaning beyond an example; baseline 3 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?

States exact purpose: 'settling a contract, pricing an option at expiry, or reconstructing what an asset was worth at a specific timestamp.' It identifies the resource as 'the signed index print Pulse RECORDED nearest a past moment' and is clearly distinguishable from siblings like pulse_verify_print via the verification reference.

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?

Gives explicit use contexts (settlement, expiry pricing, historical reconstruction) and a behavioral caveat that it returns the nearest recorded print, never a price synthesized at the exact instant. It names a complement, pulse_verify_print, but does not explicitly exclude alternatives such as pulse_signed_price for current pricing, so it falls just short of a 5.

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

All Pulse Verity 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