Skip to main content
Glama

Start a token sign-in (gate)

start_token_signin

Use when you (an agent) want to sign in to a site or API gated by TOKENLOCK, using a Bitcoin name or token your own wallet holds (for example a name bought with buy_name). Free; nothing is paid or sent. Step 1 of 2: returns challenge_id and the exact message to sign. For a TOKENLOCK site, pass its publishable site_key (pk_…, public on its sign-in page) and the site origin; the tokens it accepts come from the site. Without a site_key you can name the assets (or any_name) to get a general pass. Then sign message with your wallet (BIP-322 or legacy sign-message) and call finish_token_signin within 10 minutes. Counts as a sign-in on the site's plan only when it passes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_token_signin"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsNoWithout site_key: tokens or names that unlock (any one is enough).
originNoThe gated site's origin, e.g. https://example.com. Required with site_key.
any_nameNoWithout site_key: accept any vanity name on Bitcoin.
site_keyNoThe site's publishable key pk_… (from its sign-in page). Omit for a general pass.
pass_ttl_secondsNoHow long the pass lasts (default 900).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses that the call is free with nothing paid or sent, that it returns challenge_id and a message to sign, that the signing window is 10 minutes, and that it only counts against the site's plan when the sign-in passes. The remaining gap is whether challenges are single-use or what happens on expiry, which is minor given the hints already supplied.

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 opening clause front-loads the trigger condition, then moves through input modes, the return value, and the required follow-up step in a compact sequence. It is dense and sentence two runs long, but each clause (free/no payment, publishable key, 10-minute window, plan accounting) carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly compensates by naming the returned challenge_id and message and describing the two-step flow and time limit. The one loose end is the relationship between pass_ttl_seconds (default 900) and the 10-minute signing window, which an agent must reconcile on its own.

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%, but the description adds cross-parameter meaning the schema states only in isolation: origin is required specifically when site_key is present, site_key is a public pk_ value found on the site's sign-in page, and assets/any_name are the no-site_key alternative with 'any one is enough' semantics. pass_ttl_seconds is left entirely to the schema, so it falls just short of full coverage.

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 — starting a token sign-in gated by TOKENLOCK — and explicitly positions itself as 'Step 1 of 2' against the sibling finish_token_signin. It also names the credential source (a Bitcoin name or token your wallet holds), so an agent can distinguish it from verify, create_challenge, or check_token_access without opening schemas.

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 explicit branching conditions: pass a publishable site_key plus origin for a TOKENLOCK site, or omit it and name assets/any_name for a general pass. It also states the follow-up obligation (sign the returned message, then call finish_token_signin within 10 minutes), leaving nothing to inference about when this tool applies.

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