ko-mcp

get_crypto_holder

Read-onlyIdempotent

Get one institution's spot crypto-ETF holdings (Bitcoin ETF complex): its per-ETF positions in the latest filed quarter (shares, USD, QoQ change, action) plus its rank among all crypto-ETF holders. Use a CIK number (find it with get_crypto_holders or the search tool).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`institution`	Yes	Institution CIK number (e.g. '1512857' for Brevan Howard) or name (e.g. 'BlackRock').

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	Yes
`positions`	Yes
`requested`	Yes
`plan_limit`	Yes	The Free/keyless plan limits ko.io applied to this answer (null for paid callers)
`institution`	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": {
+    "cik": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "institution": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "latest_quarter": {
+              "$ref": "#/properties/cik"
+            },
+            "name": {
+              "$ref": "#/properties/cik"
+            },
+            "portfolio_weight_pct": {
+              "$ref": "#/properties/institution/anyOf/0/properties/total_usd"
+            },
+            "qoq_change": {
+              "$ref": "#/properties/institution/anyOf/0/properties/total_usd"
+            },
+            "rank": {
+              "anyOf": [
+                {
+                  "type": "integer"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "total_holders": {
+              "$ref": "#/properties/institution/anyOf/0/properties/rank"
+            },
+            "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": [
+            "name",
+            "latest_quarter",
+            "total_usd",
+            "qoq_change",
+            "rank",
+            "total_holders",
+            "portfolio_weight_pct"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "plan_limit": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "continuation": {
+              "$ref": "#/properties/cik"
+            },
+            "date_basis": {
+              "$ref": "#/properties/cik"
+            },
+            "effective_period": {
+              "$ref": "#/properties/cik"
+            },
+            "policy_version": {
+              "$ref": "#/properties/cik"
+            },
+            "row_cap": {
+              "$ref": "#/properties/institution/anyOf/0/properties/rank"
+            },
+            "truncated": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "window_end": {
+              "$ref": "#/properties/cik"
+            },
+            "window_start": {
+              "$ref": "#/properties/cik"
+            }
+          },
+          "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)"
+    },
+    "positions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "action": {
+            "$ref": "#/properties/cik"
+          },
+          "product_name": {
+            "$ref": "#/properties/cik"
+          },
+          "product_ticker": {
+            "$ref": "#/properties/cik"
+          },
+          "qoq_value_change": {
+            "$ref": "#/properties/institution/anyOf/0/properties/total_usd"
+          },
+          "shares_held": {
+            "$ref": "#/properties/institution/anyOf/0/properties/total_usd"
+          },
+          "usd_value": {
+            "$ref": "#/properties/institution/anyOf/0/properties/total_usd"
+          }
+        },
+        "required": [
+          "product_ticker",
+          "product_name",
+          "shares_held",
+          "usd_value",
+          "qoq_value_change",
+          "action"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "requested": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "requested",
+    "cik",
+    "institution",
+    "positions",
+    "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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds useful behavioral context beyond that: the data is scoped to the latest filed quarter, includes specific fields and a rank, and is limited to the Bitcoin ETF complex. This is meaningful supplement rather than contradiction.

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 carry a dense but focused payload: what is returned, the quarter scope, the rank, and how to resolve the input. There is no fluff, and the most important scope qualifier ('one institution's') is front-loaded.

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?

For a single-parameter tool with a 100%-covered schema, robust read-only annotations, and an output schema, the description is complete. It states the return contents, the time scope, the ranking context, and how to obtain the required identifier. Nothing essential for calling the tool correctly is missing.

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%, and the input schema already explains that 'institution' accepts a CIK number or name with examples. The description's 'Use a CIK number' adds no new semantic info; the pointer to get_crypto_holders for finding the CIK is helpful but is usage guidance rather than parameter meaning.

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?

The description clearly specifies the action ('Get'), the resource ('one institution's spot crypto-ETF holdings'), and the granularity (per-ETF positions, shares, USD, QoQ change, action, rank). The singular 'one institution's' distinguishes it from the plural sibling get_crypto_holders, so an agent can tell tools apart without opening schemas.

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 gives clear context for when to use it: to retrieve a single institution's crypto-ETF holdings. It also provides actionable input guidance by telling the agent to use a CIK number and pointing to get_crypto_holders or the search tool to find it. It does not explicitly enumerate exclusions versus all siblings, but the context is unambiguous.

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.