Skip to main content
Glama

check_access_challenge

Only for check_credits (listing a payer's Checks by wallet); paying, analysing and reading one Check need only its id. The challenge of the Check access, of its own: the text says what the signature grants (read and use the paid Checks of this wallet for 24 hours), the site and until when to sign, and that it moves no funds and authorizes no destination. chainId is any network check_info lists: on EVM it is the domain of typedData, on Solana it gives proofTransaction. Returns { nonce, message, expiresAt, buildId (check-access-), typedData (EVM) | proofTransaction (Solana) }. Sign it with prepare_signing (EVM: a signature step with typedData; Solana: the proofTransaction, never sent), then call check_access. Never use destination_challenge or destination_authorize for the Check: they do not give an access.

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_access_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.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses the semantic content of the generated challenge (grants read and use of the wallet's paid Checks for 24 hours, states site and expiry, moves no funds, authorizes no destination) and the per-chain behavior (EVM gives typedData domain, Solana gives proofTransaction). That is substantial context the annotations do not carry. It stops short of saying whether nonces expire or whether repeated calls produce distinct challenges, despite idempotentHint=false.

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?

Dense and front-loaded: scope, exclusion, content, chain handling, return shape, and next step all appear without filler. Some sentences are syntactically tangled ('The challenge of the Check access, of its own') and the closing prohibition is stated twice in effect, costing a little clarity.

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 enumerating the return object (nonce, message, expiresAt, buildId, typedData | proofTransaction). Combined with the chain-specific guidance and the required sign-then-check_access sequence, an agent has everything needed to call and use the result 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% and both params are documented, so the baseline is 3. The description nonetheless adds meaning: chainId is 'any network check_info lists,' and what chainId turns into per chain family (typedData domain on EVM, proofTransaction on Solana) — a downstream consequence the schema does not express.

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 makes clear this produces the signable access-challenge text for a paying wallet, and it explicitly scopes the tool ('Only for check_credits'). It is differentiated from check_access, destination_challenge, destination_authorize, and check_info. The framing is oblique, though — 'The challenge of the Check access, of its own' is garbled prose where a single clear verb ('builds the message the payer signs to unlock Check listing') would do the job faster.

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 when to use (listing a payer's Checks by wallet), when not to use (paying, analysing, or reading one Check need only its id), and names the alternatives to avoid (destination_challenge / destination_authorize) with the reason they don't work. It also gives the exact follow-on sequence: sign with prepare_signing, then call check_access.

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