Skip to main content
Glama
Sign In
Blink MCP Server

Blink MCP Server

Official
by blinkbitcoin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

l402_store

Manage the local L402 token cache: list cached tokens with masked secrets, retrieve a token by domain, or clear expired/all tokens.

Instructions

Manage the local L402 token cache at ~/.blink/l402-tokens.json. List cached tokens (with masked sensitive data), get a token for a domain, or clear tokens.

Input Schema

NameRequiredDescriptionDefault
domainNoDomain (hostname) for the "get" command, e.g. "stock.l402.org"
revealNoFor "get": if true, return the full unmasked preimage/macaroon (payment secrets). Default false masks them.
commandYesOperation: list all tokens, get token for a domain, or clear tokens
expired_onlyNoFor "clear": if true, only remove expired tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / domain / description
      Added value: +"Domain (hostname) for the \"get\" command, e.g. \"stock.l402.org\""
    • addedInput schema / properties / expired_only / description
      Added value: +"For \"clear\": if true, only remove expired tokens"
    • addedInput schema / properties / reveal
      Added value: +{
+  "default": false,
+  "description": "For \"get\": if true, return the full unmasked preimage/macaroon (payment secrets). Default false masks them.",
+  "type": "boolean"
+}
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that listing masks sensitive data and where the cache lives on disk, but it does not state that 'clear' is destructive/irreversible, whether clearing without a domain wipes everything, or what happens when no token exists for a domain.

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?

Two tightly written sentences: the resource and storage path are front-loaded, then the operation set. Every clause earns its place with no redundancy.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with no annotations and no output schema, the description is minimal but covers the resource and command set. It omits key behavior an agent needs: whether 'clear' is destructive/global, behavior on a cache miss for 'get', and the risk profile of exposing secrets via reveal.

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 description coverage is 100%, so the enum, domain, reveal, and expired_only semantics are already fully documented in the schema. The description adds 'masked sensitive data' as corroborating context but no information beyond what the parameter descriptions provide, so the baseline 3 applies.

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 uses a specific verb ('Manage') with a concrete resource ('local L402 token cache at ~/.blink/l402-tokens.json') and enumerates the three supported operations (list/get/clear). This clearly separates it from siblings like l402_pay or l402_discover, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It describes what each command does, which implies when to pick each one, but gives no explicit guidance on when to use this tool versus l402_pay/l402_discover or what prerequisites exist (e.g., no cached token yet). Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools