Skip to main content
Glama
stables-money

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_verification_link

Generate a KYC verification link for a customer to complete identity checks required before making transfers.

Instructions

Generate a KYC verification link for a customer. The customer must complete verification before they can make transfers.

Input Schema

NameRequiredDescriptionDefault
rejectUrlNoURL to redirect to after rejected verification
ttlInSecsNoTime-to-live for the KYC link in seconds (default: 1800)
customerIdYesThe customer ID to generate verification link for
successUrlNoURL to redirect to after successful verification
verificationTypeNoRun one verification step instead of the full flow, e.g. 'proof_of_address' when an RFI asks for it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.0
    • addedInput schema / properties / verificationType
      Added value: +{
+  "description": "Run one verification step instead of the full flow, e.g. 'proof_of_address' when an RFI asks for it",
+  "enum": [
+    "liveness",
+    "passport",
+    "source_of_wealth",
+    "proof_of_address",
+    "business_edd"
+  ],
+  "type": "string"
+}
  2. First observedv1.4.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only states that a link is generated and a precondition for transfers, but does not disclose side effects, required permissions, rate limits, link expiration behavior (despite the ttlInSecs parameter), or what happens if verification is already complete.

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 two sentences, front-loaded with the core action and followed by a key contextual constraint. Every sentence earns its place with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the basic purpose and a usage constraint, but for a tool with 5 parameters and no output schema, it omits important context such as what the returned link looks like, how long it is valid, and how the optional URLs and verificationType affect behavior.

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 all parameters. The description adds no additional meaning beyond what is in the schema (e.g., it does not explain the verificationType options or the default TTL).

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 verb (Generate) and resource (KYC verification link) for a customer, making the purpose clear. However, it does not differentiate from the sibling tool create_customer_onboarding_link, which likely has overlapping functionality.

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 the statement that the customer must complete verification before making transfers, but there is no explicit guidance on when to use this tool versus alternatives like create_customer_onboarding_link or get_kyc_capabilities, nor any exclusions.

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