Skip to main content
Glama

BTCDecoded Intelligence

by org.btcdecoded
OverviewDiscussionsAdmin

search

Read-onlyIdempotent

Cited Bitcoin coordination index. Not a live quote, ETF, derivatives, or chain analytics. 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).

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",
-  "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"
+]
  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"
-]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"
+]
  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"
-]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"
+]
  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",
-  "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"
+]
  5. Changed1 schema field changed
    • addedInput schema / properties / snapshot
      Added value: +{
+  "description": "If true, persist this result as a dated snapshot.",
+  "type": "boolean"
+}
  6. 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"
+]
  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",
-  "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"
+]
  8. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds useful context beyond that: the scope boundary against live market data and on-chain analytics, the meaning of an ok=false response, and the domain-labelling of footnotes. It does not explain the persistence semantics of snapshot or the shape of a returned passage, but the added value is genuine.

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 opening sentences are well front-loaded and the exclusions earn their place, but the body degenerates into a catalogue of individual books and authors ("Knut Svanholm Sovereignty through mathematics", "Bailey Rettler and Warmke Resistance Money", etc.) that adds length without helping an agent choose or call the tool. A grouped list of source categories would have conveyed the same coverage in a fraction of the space.

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 no output schema, the description carries responsibility for describing returns, and it only partly does so: cited passages, footnote domain labels, and the ok=false case are mentioned, but passage shape, citation format, and result limits are unaddressed. Corpus coverage and parameters are otherwise well covered.

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 baseline is 3; the description earns above that by unpacking what each source value actually contains (source=project is repos and GitHub artifacts, source=price is CoinMetrics PriceUSD, source=ln-spec is BOLTs/BLIPs/LUDs/LSP) and by describing the two-layer search model. It largely parallels the enum but supplies substantive meaning the bare labels do not.

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 a specific resource (a cited Bitcoin coordination index drawn from IRC logs, mailing lists, BIPs, Bitcoin Core source, price feeds, etc.) and explicitly carves out what it is NOT (live quote, ETF, derivatives, chain analytics). The search verb itself is only in the annotation title, and no sibling tool is named as the alternative, but the corpus scope is unmistakable.

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 "Omit to search both layers" give real operational guidance, and "If ok is false, the index has no passage" tells the agent how to interpret an empty result. However, nothing says when to reach for this versus find_discourse, find_precedent, get_passage, or verify_claim, so selection among siblings is left to inference.

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

All BTCDecoded Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources