Skip to main content
Glama

check_buy_proof

Hand here the signature of check_buy_challenge with its nonce and message, unchanged. The challenge is consumed once, the wallet goes through the free screening (OFAC, issuer freezes), and only if it passes it returns { buyProof (vcb_..., 10 minutes, secret), payer, screening: passed, expiresAt }. It reads no KYC: whether this wallet may buy Crystal is POST /v1/check/buy/kyc with the buyProof, asked only when Crystal is wanted, and check_charge refuses Crystal with kyc_required otherwise. A blocked wallet gets payer_blocked (403). A challenge of another kind (check_access_challenge, destination_challenge) is refused with check_buy_challenge_invalid. Pass buyProof to check_charge.

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": "check_buy_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYes
walletYesThe paying wallet.
messageYesFrom check_buy_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.8/5.0
Behavior5/5

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

Annotations only say this is a non-readonly, non-idempotent, non-destructive open-world call; the description goes well beyond that by disclosing that the challenge is single-use, that a screening (OFAC, issuer freezes) runs and can block the wallet, the 403 payer_blocked and check_buy_challenge_invalid failure modes, and the 10-minute expiry. Return fields are spelled out concretely for a tool with no output schema.

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?

Front-loaded with the action, then returns, then the KYC boundary, then failure codes — a sensible order with no filler sentences. The phrasing is telegraphic and slightly run-on ('It reads no KYC: whether this wallet may buy Crystal is POST ...'), and the closing 'Pass buyProof to check_charge' repeats earlier guidance.

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 5-parameter mutation-style tool with no output schema, the description supplies everything an agent needs: inputs required, what the call consumes, the shape and lifetime of the returned buyProof, screening semantics, error cases, and the downstream handoff to check_charge. Nothing material 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 already 80%, yet the description still adds meaning: 'nonce and message, unchanged' clarifies the replay contract for those parameters, and the expiry clarifies what the resulting proof token is worth. It does not, however, address the Solana path (transaction) or the wallet/payer relationship, so it improves on the schema rather than fully supplementing it.

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 action (exchange the check_buy_challenge signature for a buyProof) and a specific effect (free screening of the paying wallet), so it is clearly distinguishable from check_buy_challenge, kyc_proof and check_charge. The title and first sentence together tell an agent exactly what the call accomplishes.

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 explicitly states the precondition (signature, nonce and message from check_buy_challenge, unchanged), what to do with the result (pass buyProof to check_charge), and when NOT to use it for KYC — that is a separate /v1/check/buy/kyc step required only when Crystal is wanted. It also says challenges of other kinds are refused, which steers the agent to the correct sibling.

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