Unlock Pulse

What the data covers

get_dataset_info

Read-only

Describes the Unlock Pulse dataset itself: server version, when it was last refreshed, how many upcoming unlocks it holds and how far ahead, how many past unlocks the track record is built on, which blockchains the on-chain check covers, sources, the strength formula and thresholds, known limitations and how to cite. Use when the user asks where the numbers come from, how fresh or complete they are, or how to cite them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dataset_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`source`	Yes
`cite_as`	No
`license`	No
`sources`	Yes
`calendar`	No
`thresholds`	No
`limitations`	No
`method_page`	No
`open_dataset`	No
`track_record`	No
`on_chain_check`	No
`server_version`	Yes
`data_updated_utc`	No
`strength_formula`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026
- addedOutput schema / properties / open_dataset
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calendar": {
+      "type": "object"
+    },
+    "cite_as": {
+      "type": "string"
+    },
+    "data_updated_utc": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "license": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "limitations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "method_page": {
+      "type": "string"
+    },
+    "on_chain_check": {
+      "type": "object"
+    },
+    "server_version": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "sources": {
+      "type": "object"
+    },
+    "strength_formula": {
+      "type": "string"
+    },
+    "thresholds": {
+      "type": "object"
+    },
+    "track_record": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "source",
+    "server_version",
+    "sources"
+  ],
+  "type": "object"
+}

AddedOct 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already state readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds useful behavioral context by disclosing that the response includes known limitations and citation guidance, which signals the agent should surface caveats rather than raw numbers. It does not clarify whether the dataset descriptor is static or re-fetched per call, nor any caching or latency expectations.

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?

Purpose is front-loaded in the first clause, followed by a dense enumeration of returned fields and a separate usage sentence. Every clause maps to real content rather than filler. The field list is long enough to read as a run-on, but trimming it would lose genuine information about what the response contains.

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?

For a zero-parameter read-only metadata tool with an output schema already defined, the description covers purpose, triggering questions, and the scope of what is returned, including limitations and citation guidance. Enumerating return fields partially duplicates the output schema, but it usefully tells the agent when caveats matter. No critical gap remains for correct invocation.

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?

The tool takes zero parameters, which sets a baseline of 4, but the description makes no parameter claims at all and therefore adds nothing on this dimension. The schema is trivially complete (empty object, additionalProperties false), so there is no gap to compensate for. A neutral score reflects a dimension where the description simply has no work to do.

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 opens with a specific verb and resource ("Describes the Unlock Pulse dataset itself") and enumerates the exact contents: server version, refresh time, unlock counts, horizon, blockchains covered, sources, strength formula, limitations, citation. That is far more than a restatement of the title. It stops short of naming which sibling to use instead for overlapping topics (e.g. get_method_and_track_record, get_onchain_check), so differentiation is inferential rather than explicit.

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?

It gives concrete triggering conditions: the user asks where the numbers come from, how fresh or complete they are, or how to cite them. That is stronger than implied usage. However there are no exclusions or alternative routing, so an agent facing a question like "how is the strength score computed" must guess between this tool and get_method_and_track_record.

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

All Unlock Pulse 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.