Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

register_webhook

Register a notification webhook (free)

Registers (or replaces) an HTTPS webhook URL to receive the calling wallet's account notifications as signed POSTs — banking application status changes, bank transfer and payout completions, agent wallet deposits, card orders, and every other event the user is notified about. This closes the polling gap for agents: instead of re-fetching status endpoints, point this at any URL you can receive HTTP on (your harness's inbound webhook endpoint, or a relay you poll).

Deliveries are signed per the Standard Webhooks specification (https://www.standardwebhooks.com/): each POST carries webhook-id, webhook-timestamp, and webhook-signature (v1,<base64 HMAC-SHA256>) headers verifiable with any standard-webhooks library using the returned secret. The body is {"type": "notification.<category>", "timestamp": "<ISO 8601>", "data": {"user_id", "title", "text", "category"}}.

The secret is returned exactly once, by this call. Re-registering rotates the secret, replaces the URL, and re-enables a registration that was auto-disabled after 50 consecutive failed deliveries. Registering also notifies the account owner through their other channels and fires a first signed test delivery (type notification.account) at the new URL.

Deliveries time out after 10 seconds and are not retried; treat the webhook as a low-latency hint and the status endpoints as the source of truth. The URL must be public HTTPS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic HTTPS URL to receive signed notification POSTs. Max 512 characters. Private/internal hosts are rejected.
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": {
-    "registered": {
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "secret": {
-      "description": "Standard Webhooks signing secret (`whsec_...`). Shown only in this response — store it now. Rotate by re-registering.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "signing": {
-      "description": "Always `standard-webhooks`.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses signed delivery headers, the one-time secret, secret rotation on re-registration, auto-disable after 50 failed deliveries, a first test delivery, and 10-second timeout with no retries.

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 dense but every paragraph adds essential operational detail: delivery format, secret lifecycle, failure behavior, timeout rules, and URL requirements. The core purpose is front-loaded in the first sentence, and there is no filler.

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 there is no output schema and no annotations, the description covers the critical return value (the one-time secret), delivery payload shape, failure policy, replacement semantics, and URL constraints. An agent has enough information to invoke and understand consequences 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 description coverage is 100%, so the schema already documents both url and auth_token. The description reinforces that the URL must be public HTTPS and that private/internal hosts are rejected, but it adds no new parameter-specific semantics beyond the schema.

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 opens with a specific action+resource ('Register a notification webhook') and explains that it creates or replaces an HTTPS endpoint for signed notifications. The verb 'register' plus the described behavior clearly distinguishes it from siblings like get_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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly frames this as the push-based alternative to polling: 'instead of re-fetching status endpoints, point this at any URL you can receive HTTP on.' It does not explicitly list when not to use it or name specific sibling tools for inspecting/removing webhooks, so it stops 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 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