Skip to main content
Glama

Does an address hold a token?

check_token_access
Read-onlyIdempotent

Use before letting someone (or another agent) into something gated by a Bitcoin token or name, or before you try to sign in to a TOKENLOCK-gated site, to see whether a Bitcoin address holds that token right now. Free, read-only, no signature. Holds means the address owns the name/token or has a balance above zero. This is the same holding check TOKENLOCK runs at sign-in, but it does not prove the caller controls the address: for that, use start_token_signin/finish_token_signin (a gate pass) or create_challenge/verify_challenge.

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

Input Schema

NameRequiredDescriptionDefault
assetYesToken or name on Bitcoin, e.g. GOTPROOF or PROVEITBOT.
addressYesBitcoin address to check (bc1q, bc1p or legacy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond the annotations: it is free, read-only, requires no signature, and defines 'holds' as owning the name/token or a balance above zero. It also discloses a key limitation the annotations cannot express — that a positive result is not proof of address control. It stops short of describing behavior on unknown assets or invalid addresses.

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-loads the decision ('Use before letting someone... into something gated') and keeps everything in two tight sentences. Slightly dense with multiple sibling references, but each clause carries routing or semantic information rather than filler.

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?

For a two-parameter read-only check with no output schema, the definition covers the semantics of the result ('holds') and the safety profile well enough to call correctly. The only gap is the exact response shape, e.g. whether it returns a bare boolean or balance details, which the missing output schema leaves unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented with types, lengths and examples (bc1q/bc1p/legacy). The description adds only the notion of 'that token' for the asset argument and no format or edge-case detail beyond the schema, so baseline 3 applies.

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: check whether a Bitcoin address holds a given token/name right now. The title and first clause make the check unmistakable, and it is clearly differentiated from sign-in/proof siblings by the explicit 'does not prove control' line.

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 concrete when-to-use conditions ('before letting someone into something gated', 'before you try to sign in to a TOKENLOCK-gated site') and explicit alternatives for the adjacent case: start_token_signin/finish_token_signin or create_challenge/verify_challenge when caller control must be proven.

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