Skip to main content
Glama
stables-money

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_webhook

Subscribe to Stables events by registering an HTTPS webhook URL to receive POST notifications for selected event types, with optional HMAC-SHA256 signature verification.

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.

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.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"
+]
  2. 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')"
  3. First observedv1.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the delivery mechanism (POST requests to your URL), the signing scheme (HMAC-SHA256 via X-Webhook-Signature), and the secret's role. It omits things like whether duplicate URLs are allowed, rate limits, or what happens if the endpoint is unreachable.

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?

Three short, front-loaded paragraphs: what it does, event-type format, and security. Every sentence carries information and nothing is padded.

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 4-parameter creation tool with no output schema and no annotations, the description covers purpose, delivery semantics, and security adequately. It could go further on what is returned (webhook id/secret) and whether subscriptions can be modified later, but nothing critical to correct invocation is missing.

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 baseline is 3. The description's only extra is the note that event type strings are dotted and lowercase and that 'all' is a valid value, which is largely redundant with the enum and examples already in the schema.

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?

States a specific verb and resource: 'Subscribe to Stables events via webhook.' An agent can immediately tell this creates a webhook subscription, distinct from list_webhooks and delete_webhook. It stops short of explicitly naming those siblings as alternatives.

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?

The description implies usage (subscribe to receive POST requests for events) and gives one concrete hint, 'Use all to receive everything,' but offers no guidance on when to create a webhook versus list or delete one, nor on prerequisites such as having a reachable HTTPS endpoint.

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

Deploy Server

Other Tools