Skip to main content
Glama

Start sign-in

auth_challenge

Starts wallet sign-in: returns an EIP-4361 message for your address to sign with personal_sign, then send it to auth_verify. Proves you own the address only; never approves a payment. Free, no key. Bad address: error bad_args.

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": {
      "address": "<address>"
    },
    "name": "auth_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesTheta wallet address, 0x + 40 hex, e.g. 0xcb20457aeb7ad30dbae281efbfd7c48137db1894

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Theta wallet address, 0x + 40 hex, e.g. 0xcb20457aeb7ad30dbae281efbfd7c48137db1894"
    • addedInput schema / properties / address / 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 only declare safety flags, and the description adds real behavior: free of charge, no API key required, non-payment security scope, and the bad_args error for a malformed address. It stops short of stating whether the challenge expires or is single-use, which matters for a sign-in handshake.

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?

Three compact sentences, no filler, with the core purpose and return value front-loaded ahead of the workflow and the caveats. Every clause carries information.

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?

No output schema exists, yet the description describes the payload an agent receives (an EIP-4361 message) and the next tool to call with it, which is the critical missing piece for a single-parameter sign-in starter. Nothing essential to invoking it correctly is absent.

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?

Schema coverage is 100% with a regex pattern and example, so baseline is 3. The description supplements that with the failure mode for the single parameter ('Bad address: error bad_args'), adding meaning the schema does not carry.

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?

States a specific verb and resource ('Starts wallet sign-in') plus what it returns (an EIP-4361 message) and what it hands off to (auth_verify). An agent can distinguish it from auth_verify without opening either schema.

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?

Gives the full sequence: sign the returned message with personal_sign, then send it to auth_verify, naming the sibling used in the next step. It also bounds scope explicitly ('Proves you own the address only; never approves a payment'), so the agent knows what this flow cannot be used for.

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