Skip to main content
Glama

kyc_proof_challenge

Step one of using Crystal from an agent (owner, 17/11/2026: the API, the MCP and the CLI need the KYC for Crystal too). Crystal runs only for a wallet whose identity check (KYC) is approved, and only when the caller proves it holds that wallet. This challenge of its own, scope kyc, says the wallet is yours so Vurto may use its KYC for the analyses that require it, valid 10 minutes to sign; it moves no funds, approves no payment and authorizes no destination. chainId is any network check_info lists (it picks the family; on EVM, the typed data domain). Returns { nonce, message, expiresAt, buildId (kyc-proof-), typedData (EVM) | proofTransaction (Solana) }. Sign it with prepare_signing, then call kyc_proof. The KYC itself is done once by the person on the site; this only proves the wallet.

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": {
      "wallet": "<wallet>",
      "chainId": "<chainId>"
    },
    "name": "kyc_proof_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe wallet to prove: the receiver of the invoice, or the payer of the batch.
chainIdYesEVM: integer from GET /v1/chains (1, 10, 56, 100, 137, 8453, 42161, 43114, 130). Solana: string from GET /v1/svm/chains ("solana-mainnet").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses the 10-minute validity window, the nonce-derived buildId, the exact return shape including the EVM vs Solana variants, and a negative capability list (moves no funds, approves no payment, authorizes no destination) that lets an agent reason about risk. The readOnlyHint=false is consistent with a tool that mints challenge state while moving no value, so no contradiction arises.

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?

The important facts (step one, scope kyc, no funds move, sign then call kyc_proof) lead the text, and the return shape is placed last where it belongs. It is dense and includes an awkward parenthetical aside about the owner and date that adds noise rather than decision-relevant information.

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?

With no output schema, the description supplies the return fields itself (nonce, message, expiresAt, buildId, typedData/proofTransaction), plus expiry, the signing step, and the terminal sibling call. Nothing an agent needs to invoke this correctly in a two-parameter tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3; the description earns above that by explaining what chainId does semantically ('it picks the family; on EVM, the typed data domain'), which the schema does not state. The wallet parameter's meaning is already fully carried by the schema description, so no further addition is needed there.

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 names a specific operation (issue a signing challenge scoped to kyc) and states exactly what that challenge asserts: that the caller holds the wallet so Vurto may use its KYC. It explicitly separates this from the KYC itself ('the KYC is done once by the person on the site; this only proves the wallet'), which an agent could otherwise confuse.

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 gives an explicit position in a workflow ('step one'), the required follow-up sequence ('sign it with prepare_signing, then call kyc_proof'), and the precondition (Crystal runs only for a KYC-approved wallet). It also names the constraint on chainId ('any network check_info lists'), routing the agent to the sibling that supplies valid values.

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.

Resources