ko-mcp

get_crypto_holders

Read-onlyIdempotent

List institutional investors holding US spot crypto ETFs (Bitcoin ETF complex), ranked by total USD held, from the latest quarter of SEC 13F filings. Optionally filter to holders of a specific ETF via the product parameter (e.g. 'IBIT').

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number
`limit`	No	Results per page
`product`	No	Filter to holders of a specific spot crypto ETF ticker, e.g. 'IBIT', 'FBTC', 'GBTC'.

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	Yes
`paging`	Yes	Paging state reconciled from ko.io meta.total_count and meta.softwall
`product`	Yes
`plan_limit`	Yes	The Free/keyless plan limits ko.io applied to this answer (null for paid callers)
`total_holders`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "paging": {
+      "additionalProperties": false,
+      "description": "Paging state reconciled from ko.io meta.total_count and meta.softwall",
+      "properties": {
+        "continuation": {
+          "description": "SIGNIN_REQUIRED = page>1 needs a (free) ko.io API key",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "has_more": {
+          "description": "null = a full page came back and more MAY exist",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "next_page": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/total_holders/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Next page THIS caller can open; null when there is none (or sign-in is required)"
+        },
+        "page": {
+          "type": "integer"
+        },
+        "per_page": {
+          "type": "integer"
+        },
+        "plan_row_cap": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/total_holders/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Row cap the caller's plan applied to this page, if any"
+        },
+        "returned": {
+          "type": "integer"
+        },
+        "total_count": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/total_holders/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Total rows matching the request, when ko.io reported it"
+        },
+        "truncated_by_plan": {
+          "description": "True when the plan's row cap withheld rows from this page",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "page",
+        "per_page",
+        "returned",
+        "total_count",
+        "has_more",
+        "next_page",
+        "continuation",
+        "plan_row_cap",
+        "truncated_by_plan"
+      ],
+      "type": "object"
+    },
+    "plan_limit": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "continuation": {
+              "$ref": "#/properties/product"
+            },
+            "date_basis": {
+              "$ref": "#/properties/product"
+            },
+            "effective_period": {
+              "$ref": "#/properties/product"
+            },
+            "policy_version": {
+              "$ref": "#/properties/product"
+            },
+            "row_cap": {
+              "$ref": "#/properties/total_holders"
+            },
+            "truncated": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "window_end": {
+              "$ref": "#/properties/product"
+            },
+            "window_start": {
+              "$ref": "#/properties/product"
+            }
+          },
+          "required": [
+            "policy_version",
+            "window_start",
+            "window_end",
+            "effective_period",
+            "date_basis",
+            "row_cap",
+            "truncated",
+            "continuation"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The Free/keyless plan limits ko.io applied to this answer (null for paid callers)"
+    },
+    "product": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "cik": {
+            "$ref": "#/properties/product"
+          },
+          "name": {
+            "$ref": "#/properties/product"
+          },
+          "prev_usd": {
+            "$ref": "#/properties/rows/items/properties/total_usd"
+          },
+          "product_count": {
+            "$ref": "#/properties/total_holders"
+          },
+          "products": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "qoq_value_change": {
+            "$ref": "#/properties/rows/items/properties/total_usd"
+          },
+          "rank": {
+            "$ref": "#/properties/total_holders"
+          },
+          "total_usd": {
+            "anyOf": [
+              {
+                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
+          }
+        },
+        "required": [
+          "rank",
+          "cik",
+          "name",
+          "total_usd",
+          "prev_usd",
+          "qoq_value_change",
+          "product_count",
+          "products"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_holders": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "product",
+    "total_holders",
+    "rows",
+    "paging",
+    "plan_limit"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral context: ranking order, reliance on latest 13F filings, and optional filtering capability. It doesn't discuss pagination or output shape, but the output schema covers those, and there is no contradiction with annotations.

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 tightly written sentences deliver the core purpose, ranking, data source, and filter behavior without fluff. The most important information is front-loaded, and every clause earns its place.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich annotations, 100% parameter documentation, and an output schema, the description is fully sufficient. It explains what data is returned, the ordering, the filing period, and how to narrow results. No critical operational detail is missing for an agent to call this tool correctly.

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 description coverage is 100%, so every parameter already has a documented meaning. The description reinforces the 'product' parameter with an example ('IBIT') and places it in context, but it does not add significant new semantics beyond the schema. Baseline 3 is appropriate.

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?

Description opens with a specific verb ('List'), clearly identifies the resource ('institutional investors holding US spot crypto ETFs (Bitcoin ETF complex)'), and narrows scope with ranking ('by total USD held') and source ('latest quarter of SEC 13F filings'). This strongly differentiates it from siblings like get_crypto_holder and get_institution_holdings.

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?

The description clearly states what the tool does and provides concrete usage guidance for the optional product filter with a canonical example. It doesn't explicitly name alternatives or when-not-to-use conditions, but the context is clear enough for an agent to select this tool for the intended purpose.

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

All ko-mcp tools Inspect

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.