Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get customer

get_customer
Read-onlyIdempotent

Retrieve a customer's details and verification status by customer ID, optionally including KYC/KYB profile or document images when syncing verification data.

Instructions

Get details about a specific customer including their verification status

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": {
      "customerId": "<customerId>"
    },
    "name": "get_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoAlso return the normalized KYC/KYB data ('verification-profile') or submitted document images ('doc-images'). Slower; only to sync verification data
customerIdYesThe customer ID to look up

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.4.0
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Also return the normalized KYC/KYB data ('verification-profile') or submitted document images ('doc-images'). Slower; only to sync verification data",
+  "items": {
+    "enum": [
+      "verification-profile",
+      "doc-images",
+      "all"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  3. First observedv1.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds only that verification status is included; it does not mention the include-specific slowdown documented in the schema, but it does not contradict the annotations.

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 a single efficient sentence with the core action and key returned data front-loaded. There is no wasted wording.

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?

This is a simple two-parameter read tool with complete safety annotations and full schema descriptions. However, there is no output schema, and the description only says 'details' plus verification status, leaving the return payload broadly unspecified.

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%, and both customerId and include are documented in detail in the schema, including enum values and the 'slower; only to sync verification data' caveat. The description adds little parameter meaning beyond echoing verification status, so the baseline of 3 applies.

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 clear verb and resource: get details about a specific customer, including verification status. It does not explicitly differentiate from nearby tools such as list_customers, get_kyc_capabilities, or get_customer_rfis, so it is clear but not sibling-differentiating.

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 phrase 'specific customer' implies a single-customer lookup, but there is no explicit guidance on when to use this versus list_customers or verification-specific tools. Alternatives and exclusions are left to inference.

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