Skip to main content
Glama

Check a wallet's pass

check_pass
Read-onlyIdempotent

Reads from Base Mainnet whether a wallet holds an active 7-day pass (needed by verify_endpoint_sla), its expiry (validUntil, secondsLeft), the price (5 USDC), and the wallet's USDC balance and existing allowance to the escrow contract. Use it before verify_endpoint_sla, and after buy_pass's transactions confirm. Free and read-only.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "check_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesBase Mainnet wallet to check, e.g. "0x1234...abcd".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / walletAddress / description
      Previous value: -"Base Mainnet wallet address (0x...)"New value: +"Base Mainnet wallet to check, e.g. \"0x1234...abcd\"."
    • addedInput schema / properties / walletAddress / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint and openWorldHint, so the safety profile is known; the description still adds that it reads Base Mainnet specifically, that there is no cost, and what facts come back. The 'free and read-only' clause partly restates readOnlyHint, which keeps it from a 5.

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?

One dense sentence followed by a short ordering directive and a cost note; the capability and the returned fields are front-loaded, and every clause (chain, price, balance, allowance) 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?

There is no output schema, so the description must carry the return shape, and it does — active-pass status, validUntil, secondsLeft, price, balance and allowance. For a one-parameter read tool with annotations already declaring the safety profile, 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?

With a single fully described parameter the schema carries the burden, and the address pattern and example are already documented there. The description reinforces that the wallet must be a Base Mainnet address, which is a small but real constraint beyond 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 states a specific verb and resource — reading from Base Mainnet whether a wallet holds an active 7-day pass — and enumerates the returned facts (expiry, validUntil, secondsLeft, price, USDC balance, allowance). It is unmistakably distinct from buy_pass, which acquires the pass, and from verify_endpoint_sla, which consumes the result.

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 gives explicit ordering guidance: use this before verify_endpoint_sla and after buy_pass's transactions confirm. That names both the upstream and downstream sibling and the condition that selects each, leaving nothing to inference.

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