Skip to main content
Glama

21btc.cc Bitcoin Data

Search 21btc.cc (pages, glossary, wiki, blog)

search_site
Read-onlyIdempotent

Search the site's pages, Bitcoin glossary terms, wiki articles, blog posts, videos, pools, wallets and hacks. Matches English and Russian. Returns title, kind, URL and a short summary. Use kind=glossary for definitions. Read-only.

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_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimit to one kind of result
limitNo
queryYesWords to look for, English or Russian
languageNoLanguage of titles and summariesen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world, so the final 'Read-only' sentence is redundant. What the description does add is valuable beyond the annotations: bilingual matching across English and Russian, and the exact shape of each result (title, kind, URL, short summary). No pagination or result-count behavior is described, but the return shape disclosure is the main gap-filler.

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?

Four short sentences, front-loaded with the resource list and ending with the routing hint and safety note. The trailing 'Read-only' duplicates the annotation and is the one line that doesn't earn its place.

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

Completeness4/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 correctly compensates by naming the returned fields, and it enumerates the searchable content kinds and language behavior. It stops short of covering the limit cap (max 20) and default of 8, which an agent needs to reason about result volume.

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 75% and already documents query, kind and language enums, so the baseline is 3. The description adds meaning for the kind enum ('kind=glossary for definitions') and clarifies that matching is bilingual, but says nothing about the limit parameter or how language interacts with query matching.

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?

Opens with a specific verb (Search) and an explicit enumeration of the resource types covered (pages, glossary, wiki, blog, videos, pools, wallets, hacks), which also cleanly separates it from the sibling get_* data tools. An agent can tell instantly that this is the site-wide content lookup rather than a stats endpoint.

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?

Provides one concrete routing rule ('Use kind=glossary for definitions'), which is genuinely useful. However, there is no guidance on when not to use it, no mention of alternatives, and no note on when to prefer the language parameter over relying on bilingual matching.

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