Skip to main content
Glama

BTCDecoded Intelligence

search

Read-onlyIdempotent

Cited Bitcoin coordination index. Not a live quote, ETF, derivatives, or chain analytics. Not legal, tax, or investment advice. Pin a layer with source. If ok is false, the index has no passage. Every plan searches both layers. Footnotes label domain (protocol, lightning, mining, tooling, security, nostr, governance). Record: IRC review logs, bitcoin-dev and cryptography mailing lists, GitHub PRs/issues/commits, project repos (source=project), Delving Bitcoin, Bitcointalk, Bitcoin Stack Exchange (source=stackexchange), attributed Bitcoin talk transcripts (source=transcripts), Satoshi communications, BIP text and BIP PRs/issues, release tags/signers, and Bitcoin Core source (consensus, policy, script, validation, net, mempool, miner). Price: CoinMetrics community PriceUSD (source=price), weekly PriceUSD. Curated: named primary texts (source=articles); SatoshiLabs SLIPs (source=slips); academic protocol/security papers (source=papers); open textbooks (source=textbooks: Learning Bitcoin from the Command Line, Karasavvas, minium, Elementary Bitcoin, Dorier C#, Book of Bitcoin commentary, Mastering Bitcoin 2e, Mastering Bitcoin 3e, Mastering LN, Mastering Taproot, Luke de Wolf Defending Bitcoin, Knut Svanholm Sovereignty through mathematics, Knut Svanholm Independence Reimagined, Bailey Rettler and Warmke Resistance Money, bitcoin.org developer docs and RPC reference, Optech topics/newsletters); Nostr NIPs (source=nips); Stratum V2 spec (source=sv2); Lightning BOLTs, BLIPs, LNURL LUDs, and LSP spec (source=ln-spec); BDK, HWI, LDK, LND/CLN, miniscript, Sparrow Wallet docs (source=tooling); SeedSigner, Bitkey, and Foundation Passport docs (source=hw); specs, maps, research, and topic syntheses (source=synthesis). Legal/regulatory questions extra-pin source=legal (public opinions and agency texts) plus Legal_Exposure_Map; the search instruction carries a liability frame.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNoOptional date pin YYYY, YYYY-MM, or YYYY-MM-DD. Keeps cites whose passage date starts with that prefix. Undated cites drop.
queryYesNatural-language question or topic to retrieve cited passages for.
sourceNoOptional pin to one corpus source (e.g. github, irc, mail, price, textbooks). Omit to search both layers.
snapshotNoIf true, persist this result as a dated snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "stackexchange",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price",
      -  "transcripts",
      -  "project"
      -]New value: +[
      +  "corpus",
      +  "legal",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "repo-analysis",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "stackexchange",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts",
      +  "project"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price",
      -  "transcripts",
      -  "project"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "stackexchange",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts",
      +  "project"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price",
      -  "transcripts"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts",
      +  "project"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price"
      +]
  6. Changed1 schema field changed
    • addedInput schema / properties / snapshot
      Added value: +{
      +  "description": "If true, persist this result as a dated snapshot.",
      +  "type": "boolean"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "sv2",
      -  "ln-spec",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "sv2",
      +  "ln-spec",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price"
      +]
  9. First observed

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, non-destructive behavior, and the description adds real value on top: explicit scope exclusions (not a live quote, ETF, derivatives, or chain analytics), failure semantics ("If ok is false, the index has no passage"), dual-layer search behavior, and the fact that transcripts are attributed. Minor tension: snapshot=true persists a dated artifact while readOnlyHint=true is set, which is not reconciled. No pagination or result-size expectations are given.

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

Conciseness2/5

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

The key constraints are front-loaded, but the text then sprawls into a multi-hundred-word catalog that lists individual textbook titles ("Knut Svanholm Sovereignty through mathematics", "Dorier C#") and dozens of source tags. Much of this duplicates the enum in the schema and does not help an agent decide or invoke. The signal-to-noise ratio is poor even though some content is useful.

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?

With only four parameters, full schema coverage, and no output schema, the description does not need to explain return values — and the ok=false note covers the main failure case. What is missing is what a returned passage actually contains (fields, citation format) and how large result sets behave. Coverage of the corpus is exhaustive but lopsided against operational guidance.

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 genuinely adds meaning by mapping many enum values to concrete content (source=price is CoinMetrics PriceUSD, source=stackexchange is Bitcoin Stack Exchange, source=slips is SatoshiLabs SLIPs, etc.). The mapping is partial and inconsistent, though — a number of enum values (corpus, findings, maintainers, secsov, vision, pool, blvm-docs, governance) are never explained in prose. It says nothing about `when` or `snapshot` beyond what the schema already states.

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

Purpose3/5

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

The description frames the tool as a "Cited Bitcoin coordination index" over named corpora with cited passages, and the schema clarifies it retrieves passages for a natural-language query. But there is no crisp verb+resource statement, and nothing differentiates it from siblings like find_discourse, find_precedent, or get_passage, which plausibly search overlapping material. The bulk of the text is a corpus catalog rather than a purpose statement.

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?

"Pin a layer with source" and "Every plan searches both layers" give a workable default, and the legal/regulatory sentence gives one explicit conditional routing (extra-pin source=legal). However, there is no guidance on when to prefer this tool over the analyze_* or find_* siblings, and no advice on query formulation or result volume. Usage is implied by corpus coverage rather than stated.

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