Skip to main content
Glama

check_access

The Check access of a paying wallet, the proof check_credits asks for (access), valid 24 hours. Hand here the signature of check_access_challenge with its nonce and message, unchanged. The challenge is consumed here, once, so the access goes only to whoever holds that signature: keep it secret, it lists this payer's Checks. A challenge of another kind (destination_challenge, the claim of another charge) is refused with check_access_challenge_invalid. Returns { access, payer, expiresAt }.

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_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesFrom check_access_challenge.
walletYesThe paying wallet.
messageYesFrom check_access_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.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses the two behaviors an agent most needs: the challenge is consumed on this call and works only once (congruent with idempotentHint=false), and the resulting access is a bearer secret that exposes this payer's Checks list. It also documents the rejection path (check_access_challenge_invalid) and the return shape { access, payer, expiresAt }.

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?

Densely packed with zero filler and front-loaded with purpose and validity window. The grammar is awkward in places and several facts are packed into one long clause, but every sentence carries information an agent needs.

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, non-idempotent mutation with no output schema and no annotation-level detail, the description covers prerequisite, single-use consumption, confidentiality obligation, failure mode, and return fields. An agent needs nothing further to invoke it correctly.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already explains each parameter, and the baseline is 3. The description adds provenance semantics — signature must come from check_access_challenge and the message must be unmodified — but it leaves the optional signature and transaction parameters unexplained, so it does not fully compensate beyond what is already documented.

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 names a specific verb and resource (get the access of a paying wallet) and ties it to the sibling that consumes it (check_credits), plus a concrete lifetime of 24 hours. The opening clause is grammatically rough ("The Check access of a paying wallet"), which slightly slows recognition, but an agent can still tell this apart from check_access_challenge and check_credits.

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?

It states the precondition plainly: submit the signature produced by check_access_challenge along with its nonce and message, unchanged. It also names an exclusion — a challenge of another kind (destination_challenge, the claim of another charge) is refused with check_access_challenge_invalid. What's missing is an explicit statement of when an agent should call this versus going straight to check_credits, though the dependency chain is strongly implied.

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