Skip to main content
Glama
Stables MCP Server

Stables MCP Server

Official

Create customer onboarding link

create_customer_onboarding_link
Destructive

Create a customer and generate a hosted verification link for self-service KYC/KYB, reusing existing customers by email.

Instructions

Create a customer and get a hosted verification link for them in one call, so the customer enters their own KYC/KYB details. An existing customer with the same email is reused (customer_created is false) and the fields sent are ignored. Takes the same fields as create_customer; send what you already know.

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": {
      "customerType": "<customerType>"
    },
    "name": "create_customer_onboarding_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
dobNoDate of birth in YYYY-MM-DD format (e.g., '1990-01-15')
typeNoCompany type (e.g., 'Private Company Limited by Shares')
emailNoCustomer's email address
phoneNoPhone number with country code (e.g., '+14155552671')
taxIdNoTax ID (e.g., '12-3456789')
countryNoCountry code ISO 3166-1 alpha-2 (required for businesses, e.g., 'US')
websiteNoWebsite URL
lastNameNoLast name (required for individuals)
firstNameNoFirst name (required for individuals)
rejectUrlNoWhere to send the customer if verification is rejected
ttlInSecsNoLink lifetime in seconds (default 1800)
middleNameNoMiddle name
successUrlNoWhere to send the customer after verification succeeds
acceptTermsNoAccept Stables' terms of service and privacy policy
addressCityNoCity
companyNameNoCompany name (required for businesses)
nationalityNoTwo-letter country code (e.g., 'US', 'GB')
addressLine1NoStreet address line 1
addressLine2NoStreet address line 2
addressStateNoState or region
customerTypeYesType of customer - 'individual' for personal, 'business' for companies
entitlementsNoList of entitlements to request
sourceOfFundsNoSource of funds
accountPurposeNoWhat will you use Stables for?
addressCountryNoTwo-letter country code (e.g., 'US')
incorporatedOnNoDate of incorporation in YYYY-MM-DD format
describeBusinessNoDescription of the business
legalAddressCityNoLegal address city (for businesses)
verificationTypeNoRun one verification step instead of the full flow
addressPostalCodeNoPostal/ZIP code
legalAddressLine1NoLegal address line 1 (for businesses)
legalAddressLine2NoLegal address line 2 (for businesses)
legalAddressStateNoLegal address state (for businesses)
externalCustomerIdNoYour own reference ID for this customer
registrationNumberNoBusiness registration number
accountPurposeOtherNoExplain purpose (required if accountPurpose is OTHER)
legalAddressCountryNoLegal address country code (for businesses)
conductMoneyServicesNoWhether the company conducts money services
registrationLocationNoRegistration location (e.g., state for USA)
describeMoneyServicesNoDescribe money services (required if conductMoneyServices is true)
expectedAnnualRevenueNoEstimated annual revenue in USD
legalAddressPostalCodeNoLegal address postal code (for businesses)
expectedMonthlyPaymentsNoExpected monthly payments in USD
sourceOfFundsDescriptionNoDescribe where your business funds come from
describeComplianceControlsNoDescription of compliance controls
operateInProhibitedCountryNoDoes your business operate in any prohibited countries?
doesYourBusinessEngageInHighRiskActivitiesNoDoes your business engage in high risk activities?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / email / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • addedInput schema / properties / ttlInSecs / maximum
      Added value: +9007199254740991
  2. Addedv2.4.0

TDQS

A4.5/5.0
Behavior4/5

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

While annotations cover destructive nature, the description adds vital behavioral context by specifying the outcome: 'the customer enters their own KYC/KYB details.' This describes the resulting user journey and system state change, which is a key behavioral trait.

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 definition is extremely dense with information and perfectly structured across two sentences. Every clause serves a high-value purpose, detailing the primary function and the secondary logic (existing customer behavior).

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 its complex nature—combining onboarding, link generation, and KYC workflow—the description is exceptionally complete. It handles the core conceptual challenges of the tool, specifically the handling of existing vs. new customers.

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?

Given that schema description coverage is 100%, the description's reference to 'Takes the same fields as create_customer' is redundant, serving only as a cross-reference rather than providing unique semantic meaning to any specific parameter.

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 is highly specific, clearly stating that the tool performs a dual function: it creates a customer AND generates a hosted verification link in a single operation. This explicitly differentiates it from simple customer creation or simple link retrieval.

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?

It provides explicit guidance on behavior based on customer existence: if the email exists, it is reused (setting customer_created to false) and the provided fields are ignored. This is crucial operational logic for the agent to follow.

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