Skip to main content
Glama

create_user_request

Create a new verification request to ask another user to share verified assets. Each asset is an object naming its type, e.g. { "type": "email" }.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), or sign in with start_login — a session opens this tool — then call this tool again.

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": {
      "assets": "<assets>"
    },
    "name": "create_user_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYesAssets to request, e.g. [{ "type": "email" }, { "type": "phone", "required": false }]
partial_okNoWhether partial asset sharing is acceptable (default: false)
action_typeNoPurpose of the request (default: verification); custom and confirmation also need an action_context title
callback_urlNoHTTPS webhook URL for request status updates
redirect_urlNoHTTPS URL to redirect the subject after completing the request
reference_idNoExternal reference ID for tracking
action_contextNoWhat the recipient is shown about why the assets are needed, e.g. { "title": "Confirm your contact details" }
expires_in_hoursNoHours until request expires (default: 168, i.e. 7 days)
public_profile_idNoPublic profile ID for branding
validity_requirementNoHow recently an existing proof must have been verified for the recipient to reuse it: a number and a unit, h hours, d days, w weeks or m months (30 days), e.g. "24h", "7d", "1m"

Output Schema

NameRequiredDescriptionDefault
idNoMongoDB ObjectId
assetsNo
statusNoStatus of a verification request
outcomeNo`relying_party` when the request was created to wait for your outcome; null otherwise. Absent from an API that predates the field.
progressNo
created_atNo
expires_atNo
partial_okNo
updated_atNo
action_typeNoType of action for verification request or authorization
callback_urlNoThe webhook URL set on the request, if any
completed_atNo
redirect_urlNo
reference_idNo
action_contextNoThe action the person is asked to authorize; null when the request carries none
computed_stateNoAdditive machine-readable effective state: re-derives expiry from expires_at (never trusts the stored status). BOTH `is_expiring_soon` and `next_action` are role-aware — `next_action.role` says which side this envelope was computed for, and the two fields are consistent within it. Present only on authenticated owner/requester and recipient responses; absent on public/third-party surfaces.
verification_urlNoURL for the verification flow
validity_requirementNoRequired proof freshness as set on the request (e.g. "7d"); null when none was set
outcome_timeout_secondsNoThe window set on the request, in seconds; null when it does not wait for an outcome. Absent from an API that predates the field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / outcome
      Added value: +{
      +  "description": "`relying_party` when the request was created to wait for your outcome; null otherwise. Absent from an API that predates the field."
      +}
    • addedOutput schema / properties / outcome_timeout_seconds
      Added value: +{
      +  "description": "The window set on the request, in seconds; null when it does not wait for an outcome. Absent from an API that predates the field."
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / assets / items / properties / allowed_channels / items / enum
      Previous value: -[
      -  "whatsapp",
      -  "telegram",
      -  "sms",
      -  "email",
      -  "dns",
      -  "http",
      -  "auto",
      -  "github",
      -  "google",
      -  "facebook",
      -  "x",
      -  "linkedin",
      -  "instagram",
      -  "youtube",
      -  "tiktok",
      -  "ethereum",
      -  "solana",
      -  "bitcoin",
      -  "coinbase",
      -  "kraken",
      -  "telegram_bot_token"
      -]New value: +[
      +  "whatsapp",
      +  "telegram",
      +  "sms",
      +  "email",
      +  "dns",
      +  "http",
      +  "auto",
      +  "telegram_bot_token"
      +]
    • changedInput schema / properties / assets / items / properties / channel / enum
      Previous value: -[
      -  "whatsapp",
      -  "telegram",
      -  "sms",
      -  "email",
      -  "dns",
      -  "http",
      -  "auto",
      -  "github",
      -  "google",
      -  "facebook",
      -  "x",
      -  "linkedin",
      -  "instagram",
      -  "youtube",
      -  "tiktok",
      -  "ethereum",
      -  "solana",
      -  "bitcoin",
      -  "coinbase",
      -  "kraken",
      -  "telegram_bot_token"
      -]New value: +[
      +  "whatsapp",
      +  "telegram",
      +  "sms",
      +  "email",
      +  "dns",
      +  "http",
      +  "auto",
      +  "telegram_bot_token"
      +]
    • changedInput schema / properties / assets / items / properties / type / enum
      Previous value: -[
      -  "phone",
      -  "email",
      -  "domain",
      -  "social",
      -  "wallet",
      -  "telegram_bot"
      -]New value: +[
      +  "phone",
      +  "email",
      +  "domain",
      +  "telegram_bot"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "action_context": {
      +      "description": "The action the person is asked to authorize; null when the request carries none"
      +    },
      +    "action_type": {
      +      "description": "Type of action for verification request or authorization"
      +    },
      +    "assets": {},
      +    "callback_url": {
      +      "description": "The webhook URL set on the request, if any"
      +    },
      +    "completed_at": {},
      +    "computed_state": {
      +      "description": "Additive machine-readable effective state: re-derives expiry from expires_at (never trusts the stored status). BOTH `is_expiring_soon` and `next_action` are role-aware — `next_action.role` says which side this envelope was computed for, and the two fields are consistent within it. Present only on authenticated owner/requester and recipient responses; absent on public/third-party surfaces."
      +    },
      +    "created_at": {},
      +    "expires_at": {},
      +    "id": {
      +      "description": "MongoDB ObjectId"
      +    },
      +    "partial_ok": {},
      +    "progress": {},
      +    "redirect_url": {},
      +    "reference_id": {},
      +    "status": {
      +      "description": "Status of a verification request"
      +    },
      +    "updated_at": {},
      +    "validity_requirement": {
      +      "description": "Required proof freshness as set on the request (e.g. \"7d\"); null when none was set"
      +    },
      +    "verification_url": {
      +      "description": "URL for the verification flow"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / action_context / additionalProperties
      Removed value: -false
    • removedInput schema / properties / assets / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / callback_url / format
      Removed value: -"uri"
    • removedInput schema / properties / redirect_url / format
      Removed value: -"uri"
  4. Changed23 schema fields changed
    • addedInput schema / properties / action_context / additionalProperties
      Added value: +false
    • changedInput schema / properties / action_context / description
      Previous value: -"Additional context about why assets are needed"New value: +"What the recipient is shown about why the assets are needed, e.g. { \"title\": \"Confirm your contact details\" }"
    • addedInput schema / properties / action_context / properties
      Added value: +{
      +  "amount": {
      +    "exclusiveMinimum": 0,
      +    "type": "number"
      +  },
      +  "currency": {
      +    "maxLength": 10,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "description": {
      +    "maxLength": 500,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "entity": {
      +    "maxLength": 200,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "title": {
      +    "maxLength": 100,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +}
    • changedInput schema / properties / action_context / type
      Previous value: -"string"New value: +"object"
    • changedInput schema / properties / action_type / description
      Previous value: -"Purpose of the request (default: verification)"New value: +"Purpose of the request (default: verification); custom and confirmation also need an action_context title"
    • changedInput schema / properties / action_type / enum
      Previous value: -[
      -  "verification",
      -  "onboarding",
      -  "compliance"
      -]New value: +[
      +  "verification",
      +  "2fa",
      +  "login",
      +  "custom",
      +  "confirmation",
      +  "authorization"
      +]
    • changedInput schema / properties / assets / description
      Previous value: -"Asset type identifiers to request (e.g. email, phone, identity)"New value: +"Assets to request, e.g. [{ \"type\": \"email\" }, { \"type\": \"phone\", \"required\": false }]"
    • addedInput schema / properties / assets / items / additionalProperties
      Added value: +false
    • addedInput schema / properties / assets / items / properties
      Added value: +{
      +  "allowed_channels": {
      +    "description": "Channels the recipient may choose from",
      +    "items": {
      +      "enum": [
      +        "whatsapp",
      +        "telegram",
      +        "sms",
      +        "email",
      +        "dns",
      +        "http",
      +        "auto",
      +        "github",
      +        "google",
      +        "facebook",
      +        "x",
      +        "linkedin",
      +        "instagram",
      +        "youtube",
      +        "tiktok",
      +        "ethereum",
      +        "solana",
      +        "bitcoin",
      +        "coinbase",
      +        "kraken",
      +        "telegram_bot_token"
      +      ],
      +      "type": "string"
      +    },
      +    "maxItems": 10,
      +    "type": "array"
      +  },
      +  "channel": {
      +    "description": "Verification channel to use for this asset",
      +    "enum": [
      +      "whatsapp",
      +      "telegram",
      +      "sms",
      +      "email",
      +      "dns",
      +      "http",
      +      "auto",
      +      "github",
      +      "google",
      +      "facebook",
      +      "x",
      +      "linkedin",
      +      "instagram",
      +      "youtube",
      +      "tiktok",
      +      "ethereum",
      +      "solana",
      +      "bitcoin",
      +      "coinbase",
      +      "kraken",
      +      "telegram_bot_token"
      +    ],
      +    "type": "string"
      +  },
      +  "identifier": {
      +    "description": "The exact value to verify (e.g. an email address); omit to let the recipient choose",
      +    "maxLength": 500,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "required": {
      +    "description": "Whether this asset must be verified (default: true)",
      +    "type": "boolean"
      +  },
      +  "type": {
      +    "description": "What to verify",
      +    "enum": [
      +      "phone",
      +      "email",
      +      "domain",
      +      "social",
      +      "wallet",
      +      "telegram_bot"
      +    ],
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / assets / items / required
      Added value: +[
      +  "type"
      +]
    • changedInput schema / properties / assets / items / type
      Previous value: -"string"New value: +"object"
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for request status updates"New value: +"HTTPS webhook URL for request status updates"
    • addedInput schema / properties / callback_url / maxLength
      Added value: +2000
    • addedInput schema / properties / callback_url / pattern
      Added value: +"^https:\\/\\/"
    • changedInput schema / properties / expires_in_hours / description
      Previous value: -"Hours until request expires (default: 24)"New value: +"Hours until request expires (default: 168, i.e. 7 days)"
    • addedInput schema / properties / public_profile_id / pattern
      Added value: +"^[0-9a-fA-F]{24}$"
    • changedInput schema / properties / redirect_url / description
      Previous value: -"URL to redirect the subject after completing the request"New value: +"HTTPS URL to redirect the subject after completing the request"
    • addedInput schema / properties / redirect_url / maxLength
      Added value: +2000
    • addedInput schema / properties / redirect_url / pattern
      Added value: +"^https:\\/\\/"
    • addedInput schema / properties / reference_id / maxLength
      Added value: +255
    • addedInput schema / properties / reference_id / minLength
      Added value: +1
    • changedInput schema / properties / validity_requirement / description
      Previous value: -"Required validity level for shared assets"New value: +"How recently an existing proof must have been verified for the recipient to reuse it: a number and a unit, h hours, d days, w weeks or m months (30 days), e.g. \"24h\", \"7d\", \"1m\""
    • addedInput schema / properties / validity_requirement / pattern
      Added value: +"^\\d+[hdwm]$"
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a non-destructive write, and the description adds genuinely new context: the authentication/session requirement and the fact a login round-trip is needed before this succeeds. It restates the action_context title rule already present in the schema, but the auth disclosure is behavior an agent otherwise could not anticipate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight paragraphs; the purpose and asset shape come first and the access caveat follows. The access sentence is dense with parenthetical routing detail but every clause is actionable.

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?

An output schema exists and the 10-parameter schema is fully annotated, so the description need not explain returns or field meanings. What remains thin is the relationship to the other request-creation siblings, which for a 10-param mutation tool is the one meaningful gap.

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 every parameter including nested asset fields is documented there, so the baseline is 3. The description only echoes the asset object example already present in the schema and adds no new meaning for partial_ok, validity_requirement, or expiry.

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: 'Create a new verification request to ask another user to share verified assets', plus a concrete illustration of an asset object. It does not distinguish itself from siblings such as create_verification_request or create_multi_channel_verification, so an agent cannot tell which creation tool to pick from the description alone.

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?

Gives a real prerequisite (needs a Proof account) and a recovery path (authenticate via /mcp, or start_login opens a session, then retry). That is setup guidance, not selection guidance — nothing says when to use this instead of create_verification_request or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.