ko-mcp

search

Read-onlyIdempotent

Search across institutions, stocks, and insider traders in the ko.io SEC database. Institutions match by firm name OR manager name ('Seth Klarman' -> Baupost, 'Ackman' -> Pershing Square; person hits carry matched_person). Use this first when you have a name but need the CIK number, ticker, or slug to use with other tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max results per category
`query`	Yes	Search query — company name, ticker, person name, or institution name (min 2 characters)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`stocks`	Yes
`congress`	Yes
`insiders`	Yes
`institutions`	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": {
+    "congress": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "type": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          }
+        },
+        "required": [
+          "name",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "insiders": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "ticker": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "type": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          }
+        },
+        "required": [
+          "name",
+          "ticker",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "institutions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "aum": {
+            "anyOf": [
+              {
+                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
+          },
+          "category": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "cik": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "matched_person": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "name": {
+                    "$ref": "#/properties/institutions/items/properties/cik"
+                  },
+                  "role": {
+                    "$ref": "#/properties/institutions/items/properties/cik"
+                  }
+                },
+                "required": [
+                  "name",
+                  "role"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "rank": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "slug": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          }
+        },
+        "required": [
+          "cik",
+          "name",
+          "slug",
+          "category",
+          "aum",
+          "rank",
+          "matched_person"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "stocks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "industry": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "market_cap": {
+            "$ref": "#/properties/institutions/items/properties/aum"
+          },
+          "name": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "sector": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          },
+          "ticker": {
+            "$ref": "#/properties/institutions/items/properties/cik"
+          }
+        },
+        "required": [
+          "ticker",
+          "name",
+          "sector",
+          "industry",
+          "market_cap"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "institutions",
+    "stocks",
+    "insiders",
+    "congress"
+  ],
+  "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, openWorldHint, idempotentHint, and destructiveness false, so the description adds value by disclosing matching behavior: 'Institutions match by firm name OR manager name' and 'person hits carry matched_person'. This goes beyond annotations, revealing fuzzy matching semantics and a return-field detail, though it doesn't mention pagination or limit effects beyond the schema's limit param.

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 zero waste: the first defines scope and behavior, the second gives usage guidance and examples. The key action ('Use this first') is front-loaded. Every sentence 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 a low-complexity tool (2 params, no nested objects) with an output schema present, the description provides all necessary context: scope, matching rules, a return-field hint (matched_person), and the primary use case. Nothing an agent needs to call it 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%, so the schema already documents query and limit. The description adds examples of valid inputs (company name, ticker, person name, institution name) and clarifies match behavior, but this is modest enhancement; baseline 3 is appropriate because the schema already does the heavy lifting.

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 states it searches across institutions, stocks, and insider traders in the ko.io SEC database, with specific verb 'search' and resource. It distinguishes its purpose (finding CIK, ticker, or slug from a name) and gives concrete matching examples, separating it from the many get_* siblings that likely require identifiers.

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?

It explicitly says 'Use this first when you have a name but need the CIK number, ticker, or slug to use with other tools', which is clear when-to-use guidance. It doesn't explicitly name alternative sibling tools or provide when-not-to-use conditions, but the context implies other tools are for direct ID lookups, so it's mostly explicit but not fully exhaustive.

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.