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, Delving Bitcoin, Bitcointalk, 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), every daily close from 2010-07-18 through the last dated row, packed by ISO week. 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, 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

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

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, open-world, non-destructive), and the description adds genuinely non-obvious behavior: the two-layer model that both layers are searched unless a source pins one, and the failure contract ('If ok is false, the index has no passage'). It stops short of return format or pagination details, but the failure and layering semantics are substantive additions beyond the annotations.

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 decision-relevant facts (what it is not, layer pinning, ok=false semantics) are front-loaded, but they are followed by an exhaustive run-on catalog of sources that reads as prose documentation rather than a callable definition. The source= labeling gives some structure, yet the size is driven by enumeration rather than by what an agent needs to invoke the tool.

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 the full burden of explaining returns, and while 'Cited... index' plus 'Footnotes label domain' hints at citation structure, there is no description of result shape, ordering, or result limits. Coverage of the corpus scope and failure behavior is solid, but the output contract remains underspecified for a complex search tool.

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 description coverage is 100%, so the baseline is 3. However, the description goes further by mapping raw enum values to real meaning (source=price → CoinMetrics PriceUSD every close since 2010-07-18; source=textbooks → named titles), which an agent cannot derive from the bare enum. This is real added value over the schema.

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 opens with a noun phrase ('Cited Bitcoin coordination index') and clearly scopes what the index is not (live quote, ETF, derivatives, chain analytics), but never states the action with a verb. A reader can infer this is a retrieval/search tool over cited passages, yet nothing distinguishes it from siblings like get_passage or find_discourse without opening their schemas.

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

Usage Guidelines2/5

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

It says 'Pin a layer with source' and 'Every plan searches both layers,' which hints at the source-pinning behavior, and the 'not a live quote/ETF/derivatives' line is a useful exclusion. But there is no guidance on when to choose this tool over the many sibling retrieval tools (get_passage, find_discourse, find_precedent), leaving alternatives entirely unaddressed.

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