Skip to main content
Glama

BASE167

by com.base167

Enrol a competition wallet in Degen Games

base167_enroll_wallet

Register the wallet that will actually trade during the season. The player address is the Entry pass holder; the game wallet is the wallet whose trading gets scored.

The game wallet is judged at the OPENING BELL and must hold at least $5 USDC, no more than 0.0002 ETH of gas, and nothing else of value at that moment.

ANY wallet qualifies, including a smart account and one with a long history: there is no freshness or transaction-count rule here, only the balance at the bell.

Requires an Entry pass. Re-enrolling replaces any previous binding.

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
playerYesThe address holding the season Entry pass.
gameWalletYesThe wallet that will trade and be scored.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: it returns an unsigned transaction, never signs or holds keys, requires user approval, and is irreversible once mined. It also states the wallet is judged at the opening bell with specific balance constraints, going well beyond the structured fields.

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 detailed but every sentence serves a purpose: eligibility, constraints, prerequisites, replacement behavior, and return value. It is front-loaded with the core action and organized so critical caveats are easy to find.

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 adequately explains the return format (unsigned transaction plus voucher) and user responsibilities. It covers prerequisites, replacement semantics, irreversibility, and wallet qualification rules, making it complete enough for an agent to invoke 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% with clear descriptions for both parameters. The tool description essentially repeats that the player is the Entry pass holder and gameWallet is the scored wallet, adding little new meaning beyond the schema. The extra details about the opening bell and balances enrich context but not parameter semantics specifically.

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?

Description opens with a specific verb and resource: 'Register the wallet that will actually trade during the season.' It clearly distinguishes the player address from the game wallet and is plainly distinct from siblings like claim_entry_pass or get_leaderboard.

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?

The description gives clear context: requires an Entry pass, any wallet qualifies, and re-enrolling replaces the previous binding. It doesn't explicitly name alternative tools or say 'use this instead of X,' but the prerequisite and replacement behavior provide solid guidance.

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