Skip to main content
Glama

TOKENLOCK: plans, setup and agent use

tokenlock_info
Read-onlyIdempotent

Use when you or your operator want only holders of a Bitcoin token or name to get into a site, API, endpoint or members area, or you want to know how an agent signs in to a TOKENLOCK-gated site. Free, read-only. TOKENLOCK ("Zero-trust access for the token era") is a self-serve token gate: content stays on your own server; visitors (people or agents) "Sign in with your Token" by signing a one-time message (nothing is paid or sent) and Prove It Onchain does the token check. Returns what it is, plans and prices (unlimited sign-ins, priced by monthly active wallets: Free 1 site / 100 active wallets a month; Starter $19/month; Pro $49/month or $490/year; Business $149/month; Enterprise custom; paid in BTC), integrations with install snippets (npm @proveitonchain/tokenlock for Next.js and Express, Cloudflare Worker, PHP drop-in), a for_agents section (gate your own API; sign in with your own Bitcoin name) and links (landing, dashboard, docs, live demo).

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": "tokenlock_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is given. The description adds genuine context beyond that: the tool is free, content stays on the caller's own server, and sign-in involves signing a one-time message with nothing paid or sent. That is real added value, though it stops short of describing response structure or whether the docs returned are cached/versioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The use-case framing is correctly front-loaded, but the body is a single dense run-on that inlines the full pricing table (Free/Starter/Pro/Business/Enterprise with dollar figures and BTC payment) and package names. Since the tool returns plans and prices as content, repeating the whole ladder in the description is redundant weight that crowds out any guidance on what to do next.

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?

For a zero-parameter, read-only info tool with no output schema, the description enumerates the returned sections (plans, integrations, for_agents, links) thoroughly enough that an agent knows whether a call will answer its question. Nothing needed to invoke 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?

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter meaning is claimed or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (TOKENLOCK) and states concretely what the call yields: plans and prices, integrations with install snippets, a for_agents section and links. That is specific enough to distinguish it as a documentation/info call, but it never names the sibling tools that actually perform gating work (start_token_signin, check_token_access, verify), so differentiation is implicit rather than stated.

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 opening clause gives an explicit use case — gate a site, API, endpoint or members area by token or name holders, or learn how agent sign-in works. It is clear about context but offers no exclusions or routing, which matters here because an agent that wants to actually authenticate a visitor could mistakenly call this informational tool instead of the sign-in flow.

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