Skip to main content
Glama

kyc_proof

Hand here the signature of kyc_proof_challenge with its nonce and message, unchanged. The challenge is consumed once and it returns { walletProof (vkp_..., 30 minutes, secret), wallet, expiresAt }. Pass walletProof to invoice_create or payout_batch when they ask for "crystal" (API: header X-Wallet-Proof). It proves possession only: without an approved KYC on that wallet the call still answers kyc_required (403). A challenge of another kind is refused with kyc_proof_challenge_invalid.

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>",
      "nonce": "<nonce>",
      "message": "<message>"
    },
    "name": "kyc_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYes
walletYesThe wallet proved.
messageYesFrom kyc_proof_challenge, unchanged.
signatureNoEVM: the EIP-191 or EIP-712 signature. Solana: the ed25519 signature in base58.
transactionNoSolana: the signed proofTransaction (base64), never sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the single-use nature ('the challenge is consumed once'), the credential lifetime ('vkp_..., 30 minutes, secret'), the exact response fields, the downstream header (X-Wallet-Proof), and the two error outcomes. This is far richer than the readOnlyHint=false / idempotentHint=false flags and is consistent with them.

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 first sentence gives the action and input, the second the return value, the third the downstream use, and the last two the limits and failure modes. It is dense but every clause carries operational information, with no preamble or redundancy.

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?

For a state-mutating, non-idempotent tool with no output schema, the definition covers input provenance, consumption semantics, credential TTL, return shape, downstream consumption, and error codes. An agent could call this correctly and handle its failures without consulting anything else.

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?

With 80% schema coverage the baseline is a 3, and the description earns an upgrade by stressing that nonce and message must be forwarded unchanged from the challenge, which explains why they are required. It does not, however, mention the Solana-only 'transaction' parameter, so one fifth of the input surface is explained only by the schema.

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 opens with a specific verb and resource ('hand here the signature of kyc_proof_challenge') and is explicit about what the tool produces ('it returns { walletProof ..., wallet, expiresAt }'). It is unmistakably distinct from the sibling kyc_proof_challenge, which only issues the challenge rather than redeeming it.

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 states the exact input to supply (the challenge's signature, nonce and message, unchanged) and where the output goes next: 'Pass walletProof to invoice_create or payout_batch when they ask for "crystal"'. It also names the preconditions and failure branches (needs approved KYC, otherwise kyc_required 403; a foreign challenge yields kyc_proof_challenge_invalid), so no inference about when to call it is required.

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