Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_webhook

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

TableJSON Schema
NameRequiredDescriptionDefault
auth_tokenNoLaso credential. Only if the MCP connection has no Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it states that the signing secret is never returned, that it is shown only once at registration, and that registrations auto-disable after 50 consecutive failed deliveries. This goes beyond a generic 'get' description and surfaces critical operational behavior.

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, well-structured, and front-loaded with the main purpose. Every sentence adds meaningful information: what is returned, what is not returned, and the auto-disable behavior.

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?

The tool is simple with one optional parameter and no output schema. The description explains the core return concept, the important exception about the signing secret, and a key failure mode. It could be slightly more explicit about the full set of returned fields, but it is complete enough for safe 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 schema already documents the only parameter, auth_token, at 100% coverage. The description adds nothing about parameters, but since the schema fully covers them, the baseline of 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?

The description uses a specific verb ('Get') with a clear resource ('webhook registration & delivery health') and scopes it to the calling wallet. It also distinguishes itself from register/delete webhook siblings by clarifying what this endpoint does not do.

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?

The description implies when to use the tool: to retrieve webhook registration and delivery health. It explicitly directs users away from expecting the signing secret here and points to POST /register-webhook for secret rotation/re-registration, which is solid alternative 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 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