Skip to main content
Glama

BASE167

by com.base167

Claim a Degen Games Entry pass NFT

base167_claim_entry_pass

Claim the season Entry pass NFT, which is what lets a holder enter Degen Games. Free to eligible BASE167 holders inside the enrolment window.

Call base167_get_season first if unsure whether the window is open. After the pass is minted, the next step is base167_enroll_wallet.

This returns an UNSIGNED transaction ({chainId, to, data, value}) plus a short-lived voucher. This service never signs for the user and never holds keys. The user must approve and send the transaction from their own wallet. Once mined it CANNOT be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesAn Ethereum address on Base mainnet, 0x followed by 40 hex characters.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the tool returns an unsigned transaction plus a short-lived voucher, never signs or holds keys, requires the user to approve/send, and that the resulting on-chain action cannot be undone. This adds substantial behavioral context beyond readOnlyHint=false and destructiveHint=false.

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?

The description is front-loaded with the core purpose, then gives sequencing, return format, and safety/irreversibility warnings in a compact structure. Every sentence carries useful information without padding.

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?

With no output schema, the description properly explains what the tool returns and how the user must handle the transaction. It also covers eligibility, window checking, and the follow-up step, making it complete for an agent to invoke this tool 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 address format and requirement are already fully documented. The description does not add much parameter-specific meaning beyond the schema, though it implies the address is the user's own wallet. This meets the baseline but does not exceed 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 states a specific verb and resource: it claims the season Entry pass NFT, defines what that pass does (lets a holder enter Degen Games), and adds eligibility/free conditions. This clearly differentiates it from sibling claim tools such as base167_claim_winner_badge.

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?

Explicit sequencing is provided: call base167_get_season first if unsure whether the window is open, and base167_enroll_wallet after minting. The description also states the eligibility and enrolment-window conditions, making it clear when this tool is the appropriate step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BASE167 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: checking eligibility, claiming the token, claiming the entry pass, claiming the winner badge, enrolling, reading season state, reading leaderboard, and setting a display name. The three claim tools are clearly differentiated by their object (token, pass, badge) and by their descriptions.

Naming Consistency5/5

All tools share the base167_ prefix and follow a consistent verb_noun pattern: check_claim, claim_entry_pass, enroll_wallet, get_leaderboard, get_season, set_display_name. This makes the set predictable and easy to navigate.

Tool Count5/5

Seven tools is well-scoped for a competition lifecycle: eligibility check, claim actions, enrollment, reads, and display-name management. Each tool has a clear purpose and none feel redundant or out of place.

Completeness5/5

The tool surface covers the full user journey for BASE167 Degen Games: eligibility check, token claim, entry pass claim, wallet enrollment, season/leaderboard reads, display name setting, and winner badge claim. The absence of a prize-withdrawal tool is intentional and documented, so it is not a gap.

Resources