Laso Finance

get_webhook

Read-onlyIdempotent

Get webhook registration & delivery health (free)

Returns the calling wallet's webhook registration and its delivery health. The signing secret is never returned here — it is shown once by POST /register-webhook; re-register to rotate it.

A registration is auto-disabled after 50 consecutive failed deliveries (disabled becomes true); re-register to re-enable it.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	No
`disabled`	No	True when auto-disabled after repeated delivery failures. Re-register to re-enable.
`registered`	No
`disabled_reason`	No
`consecutive_failures`	No
`last_delivery_detail`	No	`HTTP <status>` of the last attempt, or the error message.
`last_delivery_status`	No	`delivered` or `failed`, or null before the first delivery.
`last_delivery_timestamp`	No	Epoch milliseconds of the last delivery attempt.
`last_delivery_message_id`	No	The `webhook-id` header of the last delivery.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / auth_token

Removed value: -{
-  "description": "Laso credential. Only if the MCP connection has no Authorization header.",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "consecutive_failures": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "disabled": {
+      "description": "True when auto-disabled after repeated delivery failures. Re-register to re-enable.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "disabled_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_delivery_detail": {
+      "description": "`HTTP <status>` of the last attempt, or the error message.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_delivery_message_id": {
+      "description": "The `webhook-id` header of the last delivery.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_delivery_status": {
+      "description": "`delivered` or `failed`, or null before the first delivery.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_delivery_timestamp": {
+      "description": "Epoch milliseconds of the last delivery attempt.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "registered": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "consecutive_failures": {
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "disabled": {
-      "description": "True when auto-disabled after repeated delivery failures. Re-register to re-enable.",
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "disabled_reason": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "last_delivery_detail": {
-      "description": "`HTTP <status>` of the last attempt, or the error message.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "last_delivery_message_id": {
-      "description": "The `webhook-id` header of the last delivery.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "last_delivery_status": {
-      "description": "`delivered` or `failed`, or null before the first delivery.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "last_delivery_timestamp": {
-      "description": "Epoch milliseconds of the last delivery attempt.",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "registered": {
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "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?

Beyond the readOnly/idempotent/destructive annotations, the description adds meaningful behavior: the signing secret is never returned, it is only shown once at registration, and registrations auto-disable after 50 consecutive delivery failures. This gives the agent useful operational context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the tool's purpose. The follow-up sentences each add necessary operational details, and there is no filler or redundant schema repetition.

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 no parameters, an output schema available, and annotations covering safety, the description provides everything needed to call the tool correctly. It also covers the important edge case of auto-disablement and the path to recovery.

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

Parameters4/5

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

The input schema has zero parameters, so there are no parameter semantics to document. The description still adds relevant context by clarifying that the operation applies to the calling wallet's webhook, which is the only implicit input.

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 gives a specific verb and resource: 'Get webhook registration & delivery health.' It also scopes the operation to 'the calling wallet's' webhook, making the read-only intent unambiguous and clearly distinguishing it from sibling tools like register_webhook and delete_webhook.

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 routes the agent away from this tool when the signing secret is needed or when rotation is desired, pointing to POST /register-webhook instead. It also explains that a disabled registration must be re-registered to re-enable, giving concrete when-not-to-use guidance.

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

All Laso Finance 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.

Resources

Need Help?