Skip to main content
Glama

BASE167

by com.base167

Set a Degen Games display name or X handle

base167_set_display_name

Set the display name or X handle shown next to a wallet on the boards.

This is the one action that needs a signature FROM THE USER'S OWN WALLET, so it runs in two steps:

  1. Call with address and name (or handle) and NO signature. The tool returns the exact message to sign and the expiry it was built with.

  2. Have the user sign that message byte for byte, then call again with the signature and the SAME expiry.

The message must match exactly or the answer is 401. Both plain wallets and smart contract wallets are accepted.

Set EXACTLY ONE of name or handle per call -- they are separate actions on separate routes, signed with deliberately different message prefixes so a signature captured for one can never be replayed as the other. Passing both is refused rather than guessed at. The expiry from step 1 is valid for at most 900 seconds; an open-ended one is rejected, not ignored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name, up to 24 printable ASCII characters. Mutually exclusive with handle.
expiryNoThe expiry returned by step 1, echoed back unchanged. Omit on step 1. At most 900 seconds ahead of now -- a longer window is rejected, not clamped.
handleNoX handle without the @, up to 15 characters. Mutually exclusive with name.
addressYesAn Ethereum address on Base mainnet, 0x followed by 40 hex characters.
signatureNoThe signature over the returned message. Omit on step 1.

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedInput schema / properties / expiry / description
      Previous value: -"The expiry returned by step 1. Omit on step 1."New value: +"The expiry returned by step 1, echoed back unchanged. Omit on step 1. At most 900 seconds ahead of now -- a longer window is rejected, not clamped."
    • changedInput schema / properties / handle / description
      Previous value: -"X handle without the @, up to 15 characters."New value: +"X handle without the @, up to 15 characters. Mutually exclusive with name."
    • changedInput schema / properties / name / description
      Previous value: -"Display name, up to 24 printable ASCII characters."New value: +"Display name, up to 24 printable ASCII characters. Mutually exclusive with handle."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses critical behaviors: the need for a user's own wallet signature, the two-step flow, exact message matching or 401, support for smart contract wallets, mutual exclusivity of name/handle to prevent replay, the 900-second expiry validity, and rejection of open-ended expiries. This is rich behavioral context that annotations alone do not provide.

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?

The description is moderately long but every sentence carries necessary information. It is logically structured: first a one-line summary, then the two-step procedure, followed by security and constraint details. No filler, but it could be slightly tightened without losing critical warnings.

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?

Given the absence of an output schema, the description compensates by providing all essential operational details: the request/response expectation (message to sign and expiry), error behavior (401), time limits, and input constraints. An agent can correctly execute both steps without needing additional information.

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?

The schema already covers all parameters with descriptions (100% coverage), which warrants a baseline of 3. The description adds extra context beyond the schema: it explains the two-step flow's implications for expiry and signature, and clarifies that the mutual exclusivity of name/handle is enforced and why. This adds genuine semantic value.

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 ('Set') and resource ('the display name or X handle shown next to a wallet on the boards'), clearly distinguishing this from sibling tools like claim_entry_pass or get_leaderboard. It also clarifies the two-step nature, making the purpose unmistakable.

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 provides detailed step-by-step instructions on how to call the tool, including when to omit or include signature/expiry. It explicitly says to set exactly one of name or handle, and warns against passing both. While it does not name alternative tools for when not to use this, the context is clear enough for correct invocation.

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