Skip to main content
Glama

21btc.cc Bitcoin Data

Upcoming Bitcoin conferences and events

get_events
Read-onlyIdempotent

Upcoming Bitcoin-only conferences with dates, city, official URL, ticket offer (price only where verified on the official page) and the 21btc.cc event page where one exists. Dates in the venue's local time. 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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
countryNoFilter by country name in English, e.g. Switzerland

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds real context beyond that: prices are only shown when verified on the official page, dates are in venue-local time, and only upcoming events are returned.

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?

A single dense sentence, front-loaded with purpose and the field list. The trailing 'Read-only' restates the annotation and is slightly wasteful, but overall it is efficient.

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 usefully explains what each event record contains. It does not explain pagination, the default limit, or what happens when 'limit' is exceeded, which leaves a small gap for a two-parameter listing tool.

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?

Schema coverage is only 50%: 'country' is documented in the schema, but 'limit' has no description anywhere. The description does not mention either parameter, so it fails to compensate for the undocumented limit or explain filtering and default behavior.

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?

States a specific verb and resource ('Upcoming Bitcoin-only conferences') and enumerates the returned fields (dates, city, official URL, ticket price, event page). This clearly distinguishes it from the sibling tools, which are all price/network/metric lookups.

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?

The 'Bitcoin-only' and 'upcoming' framing implies scope, but the description never says when to use this versus alternatives or when not to use it. Sibling tools are unrelated, so no explicit routing is required, but no usage guidance is offered either.

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