Skip to main content
Glama
Sign In
CoinBucha

CoinBucha

by jukkablomberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_treasury_holdings

Retrieve corporate Bitcoin treasury data: total BTC held by public companies and top holders.

Instructions

Corporate Bitcoin treasury holdings: total BTC held by public companies + top holders.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It describes only the data content, not behavioral traits such as read-only nature, rate limits, or output structure. It provides minimal behavioral disclosure beyond the fact that it exposes these holdings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the key concept and contains no wasted words.

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?

For a zero-parameter tool with no output schema, the description gives a general sense of the return (total BTC and top holders) but leaves ambiguity about the composition of 'top holders' and the exact list of public companies. It is acceptable but not fully detailed.

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?

The tool has zero parameters, so the baseline is 4. The description appropriately focuses on the output data, and no parameter explanation is needed.

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 clearly states the tool covers corporate Bitcoin treasury holdings with total BTC held by public companies and top holders. This distinguishes it from siblings like sovereign_reserves and etf_flows, but it lacks an explicit verb, though the name 'get_' implies retrieval.

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 subject matter implies when to use it (when needing corporate treasury holdings), but there is no explicit guidance on when not to use it or alternatives. The description does not reference sibling tools.

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

Deploy Server

Other Tools