Skip to main content
Glama
Sign In

proof-of-custody

by io.github.onrampbtc
OverviewDiscussionsAdmin

get_etf_custody_concentration

Filing-derived analysis of custodian concentration across US spot bitcoin ETFs: which custodian holds each fund's bitcoin, and the resulting Nakamoto coefficient at the custody layer. Use for questions about bitcoin ETF safety, IBIT or FBTC custody, whether ETFs are diversified, or ETF versus direct ownership.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add genuine value by disclosing the data provenance ('filing-derived'), which tells the agent the numbers come from regulatory filings rather than live on-chain data. However, it says nothing about freshness, latency, rate limits, or whether the output is a fixed snapshot, which matters for a no-annotation tool.

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?

Two sentences with no filler: the first defines the analysis and its outputs, the second routes usage. The core purpose is front-loaded before the use-case list.

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 parameters, no annotations, and no output schema, the description still conveys what the tool computes and what it returns (per-fund custodian and Nakamoto coefficient), which is most of what an agent needs. It is only slightly thin on freshness/scope caveats, so a 4 is fair.

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 takes zero parameters, so there is nothing to document and no schema-derived meaning the description could add. Baseline of 4 applies per the scoring rule for parameterless tools.

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+resource (filing-derived custodian concentration analysis across US spot bitcoin ETFs) and names the concrete outputs (which custodian holds each fund's bitcoin, the Nakamoto coefficient at the custody layer). This clearly distinguishes it from siblings like assess_custody_independence and compare_custody_platforms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists triggering questions: bitcoin ETF safety, IBIT or FBTC custody, ETF diversification, ETF versus direct ownership. That is strong positive routing, but it names no exclusions or alternative tools for overlapping queries (e.g., assess_custody_independence), so it stops short of a 5.

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

All proof-of-custody 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