Skip to main content
Glama

Finish a token sign-in (get a pass)

finish_token_signin

Use after start_token_signin, once your wallet has signed the message. Free. Checks the signature and that the address holds an accepted token or name right now, and returns a short-lived pass (pp1.…). Give the pass to the gated site the way it asks: sites using the npm package or Cloudflare template take it at POST /api/tokenlock/session ({"pass": "…"}) and set a cookie; your own API can take it in a header and check it with verifyPass. If the site accepts any name, send your name. Single use per challenge. A pass proves you controlled a wallet holding the token at sign-in, not who you are.

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": {
      "challenge_id": "<challenge_id>",
      "address": "<address>",
      "signature": "<signature>"
    },
    "name": "finish_token_signin"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour vanity name, when the site accepts any name.
addressYesThe Bitcoin address that signed.
signatureYesBase64 signature of the exact message (BIP-322 or legacy sign-message).
challenge_idYeschallenge_id from start_token_signin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing cost (Free), single-use semantics per challenge, pass lifetime (short-lived), the pp1.… format, and the exact security meaning of a pass (wallet control at sign-in, not identity). It does not describe failure modes for an invalid signature or a non-holding address beyond implying rejection, which keeps it just short of a 5.

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?

Front-loaded with timing, cost and effect, then delivery mechanics. Every sentence carries information, though the endpoint/header integration detail is denser than strictly needed for tool selection.

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, and the description compensates by describing the returned artifact (a short-lived pp1. pass) and how to consume it. For a 4-param, single-use challenge-completion tool with annotations covering the mutation profile, nothing an agent needs is missing.

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%, so the baseline is 3, but the description adds real meaning: it clarifies that `address` must currently hold an accepted token or name, and gives a usage condition for `name` that the schema only hints at ('when the site accepts any name').

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 outcome: it checks a signature plus current token/name holdings and returns a short-lived `pass` (pp1.…). It also anchors itself to the sibling `start_token_signin` as the required predecessor, so an agent can place it in the flow immediately.

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 ('Use after start_token_signin, once your wallet has signed the message'), an explicit conditional for the optional `name` param ('If the site accepts any name, send your name'), and concrete downstream delivery options including the npm/Cloudflare endpoint and the verifyPass route for custom APIs.

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