Skip to main content
Glama

California Bitcoin

by org.californiabitcoin
OverviewDiscussionsAdmin

Get Bitcoin Topic

get_bitcoin_topic
Read-onlyIdempotent

FREE. FREE, no account required. Retrieve one canonical Knowledge Atlas topic with sources, provenance and related concepts. Inspect a known canonical topic in depth before deciding whether paid evidence packaging is necessary. Use only when the canonical topic id is already known. Do not use this as free-text search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCanonical Knowledge Atlas topic identifier, using lowercase letters, numbers, and hyphens.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / description
      Added value: +"Input for Get Bitcoin Topic. Use the documented fields exactly; unknown fields are rejected."
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "proof-of-work"
+  }
+]
    • addedInput schema / properties / id / examples
      Added value: +[
+  "proof-of-work"
+]
  2. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, trust, and next-step fields."New value: +"Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, freshness, trust, and next-step fields."
  3. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Canonical Knowledge Atlas topic identifier, using lowercase letters, numbers, and hyphens."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured California Bitcoin result with operation-specific research, evidence, provenance, coverage, trust, and next-step fields.",
+  "type": "object"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds value by disclosing that the tool is free/no-account, returns a single canonical topic, and includes sources, provenance, and related concepts.

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?

The description is short and front-loads the most important facts, but 'FREE. FREE, no account required.' is redundant and could be condensed. The rest is efficient and useful.

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

Completeness5/5

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

This is a simple one-parameter tool with a full output schema and annotations covering idempotence and safety. The description fully explains when to invoke it, what it returns, and how it differs from search and paid evidence packaging.

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%, and the schema already documents the id format, pattern, max length, and canonical nature. The description reinforces that the id must be a canonical topic id rather than free text, but it adds no format details beyond the schema.

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?

The description uses a specific verb ('Retrieve') with a precise resource ('one canonical Knowledge Atlas topic with sources, provenance and related concepts'). It explicitly contrasts with free-text search, distinguishing it from search_bitcoin_knowledge.

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?

The description clearly states when to use it: 'Use only when the canonical topic id is already known.' It also gives the decision context ('before deciding whether paid evidence packaging is necessary') and an explicit exclusion: 'Do not use this as free-text search.'

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

All California Bitcoin 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