Skip to main content
Glama

check_buy_challenge

Step one of buying a Check (owner, 12/11/2026: only a wallet that passes the free screening buys, so it signs first). The challenge of its own, scope buy: the text says this wallet pays for a Check and is screened before buying, valid 10 minutes, and that it moves no funds and authorizes no destination. chainId is any network check_info lists. Returns { nonce, message, expiresAt, buildId (check-buy-), typedData (EVM) | proofTransaction (Solana) }. Sign it with prepare_signing, then call check_buy_proof.

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

Input Schema

NameRequiredDescriptionDefault
walletYesThe paying wallet.
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.2/5.0
Behavior5/5

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

Annotations mark this as a non-idempotent, non-readonly mutation, and the description supplies the context an agent needs to trust it: the challenge expires in 10 minutes, moves no funds, and authorizes no destination. It also enumerates the response shape, including the buildId format and the EVM typedData vs Solana proofTransaction split, which is behavior no annotation conveys.

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

Conciseness3/5

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

Information is front-loaded and dense with no filler, but some sentences are awkward to the point of ambiguity, e.g. "The challenge of its own, scope buy" and the clipped aside about an owner and a date. Tightening the grammar would preserve the content while reducing parsing effort.

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?

There is no output schema, and the description compensates by describing the return fields and their per-chain variation. Combined with the expiry, safety statement, and next-step handoff, an agent has everything needed to invoke this correctly.

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 both parameters are already documented. The description still adds routing value by tying chainId to the networks check_info lists, and by noting the payload differs by chain family. It adds modest meaning beyond the schema rather than restating it.

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?

The description states a specific action and resource: it issues a buy challenge (a signed message/nonce) for a Check, and explicitly frames it as "step one" ahead of check_buy_proof. That sequencing makes it distinguishable from the sibling that completes the purchase. The phrasing "The challenge of its own, scope buy" is slightly garbled but the intent remains recoverable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear workflow routing: sign the result with prepare_signing, then call check_buy_proof, and use chainId values that check_info lists. It also states the precondition that only a wallet passing the free screening buys. It does not state when this step can be skipped or what to do on failure, so it falls short of explicit exclusions.

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