Skip to main content
Glama
Stables MCP Server

Stables MCP Server

Official

Create webhook

create_webhook
Destructive

Create a webhook to receive POST notifications for selected Stables events at your HTTPS URL. Set a secret to verify HMAC-SHA256 signatures.

Instructions

Subscribe to Stables events via webhook. You'll receive POST requests to your URL when events occur.

Event types are dotted and lowercase. Use 'all' to receive everything.

Security: Set a secret to enable HMAC-SHA256 signature verification via X-Webhook-Signature header.

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": {
      "name": "<name>",
      "url": "<url>",
      "eventTypes": "<eventTypes>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe HTTPS URL to receive webhook POST requests
nameYesA descriptive name for this webhook (e.g., 'Transfer status notifications')
secretNoOptional signing secret for HMAC-SHA256 webhook signature verification
eventTypesYesEvent types to subscribe to (e.g. ['transfer.updated.status_transitioned']), or ['all']

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv2.5.1
    • changedInput schema / properties / eventTypes / items / enum
      Previous value: -[
      -  "customer.created",
      -  "customer.updated",
      -  "kyc_link.updated.status_transitioned",
      -  "transfer.created",
      -  "transfer.updated.status_transitioned",
      -  "quote.created",
      -  "quote.updated.status_transitioned",
      -  "virtual_account.created",
      -  "virtual_account.activity.created",
      -  "virtual_account.activity.updated.status_transitioned",
      -  "travel_rule.wallet_verification_required",
      -  "rfi.created",
      -  "rfi.updated",
      -  "rfi.resolved",
      -  "all"
      -]New value: +[
      +  "customer.created",
      +  "customer.updated",
      +  "kyc_link.updated.status_transitioned",
      +  "transfer.created",
      +  "transfer.updated.status_transitioned",
      +  "transfer.action_required",
      +  "quote.created",
      +  "quote.updated.status_transitioned",
      +  "virtual_account.created",
      +  "virtual_account.activity.created",
      +  "virtual_account.activity.updated.status_transitioned",
      +  "virtual_account.fee_charge_failed",
      +  "virtual_account.deactivated",
      +  "virtual_account.reactivated",
      +  "travel_rule.wallet_verification_required",
      +  "rfi.created",
      +  "rfi.updated",
      +  "rfi.resolved",
      +  "entitlement.requested",
      +  "entitlement.updated.status_transitioned",
      +  "entitlement.updated.requirements_changed",
      +  "prefund.wallet.created",
      +  "prefund.deposit.received",
      +  "prefund.withdrawal.completed",
      +  "prefund.withdrawal.failed",
      +  "all"
      +]
  3. Changed3 schema fields changedv2.4.0
    • changedInput schema / properties / eventTypes / description
      Previous value: -"List of event types to subscribe to (e.g., ['WEBHOOK_EVENT_TYPE_PAYMENT_STATUS_CHANGED'])"New value: +"Event types to subscribe to (e.g. ['transfer.updated.status_transitioned']), or ['all']"
    • addedInput schema / properties / eventTypes / items / enum
      Added value: +[
      +  "customer.created",
      +  "customer.updated",
      +  "kyc_link.updated.status_transitioned",
      +  "transfer.created",
      +  "transfer.updated.status_transitioned",
      +  "quote.created",
      +  "quote.updated.status_transitioned",
      +  "virtual_account.created",
      +  "virtual_account.activity.created",
      +  "virtual_account.activity.updated.status_transitioned",
      +  "travel_rule.wallet_verification_required",
      +  "rfi.created",
      +  "rfi.updated",
      +  "rfi.resolved",
      +  "all"
      +]
    • changedInput schema / properties / name / description
      Previous value: -"A descriptive name for this webhook (e.g., 'Payment Status Notifications')"New value: +"A descriptive name for this webhook (e.g., 'Transfer status notifications')"
  4. First observedv1.4.0

TDQS

A3.7/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations: outbound POST delivery to the configured URL, event type formatting, use of 'all', and HMAC-SHA256 signature verification via a secret. It does not discuss idempotency or the consequences of destructiveHint=true, but the annotations already carry the safety profile.

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 definition is short and front-loaded, with useful delivery, event-type, and security notes. The event-type sentence partly repeats the enum and schema description, which keeps it just short of ideal conciseness.

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 webhook creation tool with complete schema coverage and annotations, the description covers the essential behavior: POST delivery, event type syntax, and signature verification. It omits response details, but no output schema exists and the core invocation context is present.

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 the schema already documents url, name, secret, and eventTypes. The description reinforces event type format and the 'all' option, but adds little parameter semantics beyond what is already structured.

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 states a specific action and resource: subscribing to Stables events via webhook, with POST delivery to a URL. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as list_webhooks or 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 Guidelines3/5

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

Usage is implied by 'Subscribe to Stables events via webhook' and the delivery behavior, but there is no explicit guidance on when to create a webhook versus using list_webhooks or delete_webhook. Prerequisites such as endpoint readiness are also left implicit.

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