Skip to main content
Glama

21btc.cc Bitcoin Data

Site changelog

get_changelog
Read-onlyIdempotent

Recent shipped changes to 21btc.cc with dates and links. Same data as the /changelog page and its RSS feed. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_changelog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' merely repeats structured data. What does add value is disclosing the content shape (dates and links) and the source-of-truth equivalence to the /changelog page and RSS feed, though nothing is said about ordering, freshness, or pagination behavior.

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?

Three short, front-loaded sentences that put the resource and content first. The trailing 'Read-only.' duplicates the annotation and is the only wasted sentence.

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?

For a zero-required-param read tool with no output schema, the description covers what is returned (changes with dates and links) and where the same data lives. Only the meaning and bounds of 'limit' are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'limit' parameter has 0% schema description coverage and is never mentioned in the description; 'Recent shipped changes' only loosely implies newest-first ordering. The agent must infer from the schema's default of 10 and max of 50 that limit controls how many entries are returned.

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 (shipped changes to 21btc.cc) and what it contains (dates and links), which is clearly distinct from all siblings like get_price, get_network_stats, or search_site. It stops short of explicitly contrasting with a sibling, but the resource is unambiguous.

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?

Saying the data matches the /changelog page and RSS feed tells the agent what the content is, implying usage for 'what's new' questions, but it never states when to choose this over search_site or another tool, nor any exclusions. Usage 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources