Client Profile
get_client_profileCanonical MCP read for your profile or a profile view for a client/member you can access. Advisors use active relationships, coaches follow managed-program defaults, and scoped admins can use debugAccess for read-only break-glass when eligible. Professional responses may include bounded shared member intelligence such as document-backed facts when policy allows. currentFacts for a professional are the facts the client marked shared with you plus facts X1 read from documents shared with you, with document, page, and section but never quoted text.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_client_profile"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| clientId | No | Client or member user ID. Professionals must pass it unless X1 already supplied a client-scoped context. | |
| clientEmail | No | Client or member email | |
| debugAccess | No | Admin-only read-only break-glass escalation. Mirrors the coach profile route debugAccess pattern when your entitlements allow it. |