Skip to main content
Glama
pulse-verity

pulse-verity

Get Recorded Print

get_recorded_print
Read-onlyIdempotent

Fetches the recorded signed index print nearest a requested ISO-8601 or epoch time for a crypto symbol, so you can verify historical prices and check deltaMs before trusting fields.

Instructions

Get the recorded signed index print nearest a requested time from /api/index/v1/print. Accepts ISO-8601 or epoch milliseconds. Check deltaMs: it is the distance between your requested time and the sampled print. Sampling and retention are bounded; a recorded print need not equal a separate live read. Preserve the whole print, including priceText, kid and v2, for verify_print. Require recordValid=true before trusting quality fields. Request-envelope fields such as deltaMs are unsigned. Needs a developer key (PULSE_API_KEY) or the hosted server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "at": "<at>"
    },
    "name": "get_recorded_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesThe moment to look up: ISO-8601 (e.g. 2026-11-11T17:00:00Z) or epoch milliseconds
symbolYesCrypto ticker symbol, e.g. BTC, ETH, SOL

Output Schema

NameRequiredDescriptionDefault
atNo
v2No
kidNo
sigNo
kindNo
noteNo
tierNo
errorNo
gradeNo
priceNo
engineNo
getKeyNo
sampleNo
symbolNo
assetIdNo
cadenceNo
deltaMsNo
sourcesNo
successNo
closeDayNo
intervalNo
priceTextNo
requestIdYesIdentifier for this MCP call; not a signed price field.
signatureNo
confidenceNo
dispersionBpsNo
qualityRecordedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv1.3.7
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / at / description
      Added value: +"The moment to look up: ISO-8601 (e.g. 2026-11-11T17:00:00Z) or epoch milliseconds"
    • changedOutput schema / properties / cadence / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "band": {
      -        "enum": [
      -          "real-time",
      -          "five-second",
      -          "ten-second",
      -          "slow",
      -          "unavailable"
      -        ],
      -        "type": "string"
      -      },
      -      "calculatedAgeMs": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "newestSourceAgeMs": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "oldestSourceAgeMs": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "p50UpdateMs": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "p95UpdateMs": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "updatesLast120s": {
      -        "$ref": "#/properties/sources/anyOf/0"
      -      }
      -    },
      -    "required": [
      -      "band"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "band": {
      +        "enum": [
      +          "real-time",
      +          "five-second",
      +          "ten-second",
      +          "slow",
      +          "unavailable"
      +        ],
      +        "type": "string"
      +      },
      +      "calculatedAgeMs": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "newestSourceAgeMs": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "oldestSourceAgeMs": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "p50UpdateMs": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "p95UpdateMs": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "updatesLast120s": {
      +        "maximum": 9007199254740991,
      +        "minimum": 0,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "band"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / confidence / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / confidence / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / dispersionBps / anyOf
      Removed value: -[
      -  {
      -    "$ref": "#/properties/confidence/anyOf/0"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dispersionBps / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / interval / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "lower": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "upper": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/confidence/anyOf/0"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "required": [
      -      "lower",
      -      "upper"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "lower": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "upper": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "lower",
      +      "upper"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / requestId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedOutput schema / properties / sources / anyOf
      Previous value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / v2 / properties / kid / $ref
      Removed value: -"#/properties/kid"
    • addedOutput schema / properties / v2 / properties / kid / pattern
      Added value: +"^[A-Za-z0-9._:-]{1,64}$"
    • addedOutput schema / properties / v2 / properties / kid / type
      Added value: +"string"
    • removedOutput schema / properties / v2 / properties / signature / $ref
      Removed value: -"#/properties/signature"
    • addedOutput schema / properties / v2 / properties / signature / maxLength
      Added value: +88
    • addedOutput schema / properties / v2 / properties / signature / minLength
      Added value: +88
    • addedOutput schema / properties / v2 / properties / signature / pattern
      Added value: +"^[A-Za-z0-9+/]{86}==$"
    • addedOutput schema / properties / v2 / properties / signature / type
      Added value: +"string"
  2. Addedv1.3.6

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that sampling and retention are bounded, that the nearest match may not equal a live read, that deltaMs must be checked, that recordValid gates the quality fields, and that auth via PULSE_API_KEY is required. What is missing is any statement of rate limits or failure behavior when no print falls in the retention window.

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 core purpose is front-loaded in the first sentence, and the caveats are ordered by importance (deltaMs, retention, preserve-for-verify, recordValid, auth). It is dense but nearly every sentence carries operational value; only the 'request-envelope fields are unsigned' note is marginal.

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 already defines the return shape, the description covers the remaining risks: auth requirements, sampling/retention limits, validation gating, and how to hand off to verify_print. Nothing an agent needs before calling is absent.

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%, so 'at' and 'symbol' are already fully documented; the description only repeats the accepted time formats. Its added value concerns response fields (deltaMs, recordValid) rather than input parameters, so the baseline of 3 applies.

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 a specific verb and resource ('Get the recorded signed index print nearest a requested time') plus the backing endpoint, so the agent knows exactly what is returned: a time-matched signed print. It also names verify_print as the downstream consumer, which separates it from the other lookup tools.

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 clear context for use (a specific moment, nearest-sampled match) and an explicit downstream route ('Preserve the whole print ... for verify_print'). It does not explicitly exclude sibling lookups such as get_index_price or get_settlement_print, so the agent must infer which one fits.

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