Skip to main content
Glama

list_institutions

Read-onlyIdempotent

List top institutional investors (hedge funds, mutual funds, etc.) tracked in the SEC 13F database. Supports search by name and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
limitNoResults per page
searchNoSearch by institution name, CIK, or manager name (e.g. 'Klarman' -> Baupost)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
pagingYesPaging state reconciled from ko.io meta.total_count and meta.softwall
searchYes
plan_limitYesThe Free/keyless plan limits ko.io applied to this answer (null for paid callers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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/rows/items/properties/rank/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/rows/items/properties/rank/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/rows/items/properties/rank/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/search"
      +            },
      +            "date_basis": {
      +              "$ref": "#/properties/search"
      +            },
      +            "effective_period": {
      +              "$ref": "#/properties/search"
      +            },
      +            "policy_version": {
      +              "$ref": "#/properties/search"
      +            },
      +            "row_cap": {
      +              "$ref": "#/properties/rows/items/properties/rank"
      +            },
      +            "truncated": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "window_end": {
      +              "$ref": "#/properties/search"
      +            },
      +            "window_start": {
      +              "$ref": "#/properties/search"
      +            }
      +          },
      +          "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)"
      +    },
      +    "rows": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "category": {
      +            "$ref": "#/properties/search"
      +          },
      +          "cik": {
      +            "$ref": "#/properties/search"
      +          },
      +          "name": {
      +            "$ref": "#/properties/search"
      +          },
      +          "portfolio_value": {
      +            "anyOf": [
      +              {
      +                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
      +          },
      +          "rank": {
      +            "anyOf": [
      +              {
      +                "type": "integer"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "slug": {
      +            "$ref": "#/properties/search"
      +          },
      +          "stock_count": {
      +            "$ref": "#/properties/rows/items/properties/rank"
      +          }
      +        },
      +        "required": [
      +          "cik",
      +          "name",
      +          "slug",
      +          "rank",
      +          "category",
      +          "portfolio_value",
      +          "stock_count"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "search": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "search",
      +    "rows",
      +    "paging",
      +    "plan_limit"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Search by institution or founder name"New value: +"Search by institution name, CIK, or manager name (e.g. 'Klarman' -> Baupost)"
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side-effect expectations. The description adds useful behavioral context about data source (SEC 13F) and search/pagination support, but it does not disclose ordering, default limits, or any rate-limit behavior beyond the schema.

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 concise sentences with the core action front-loaded. There is zero filler, and the additional capability note (search + pagination) is placed second without redundancy.

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?

For a simple read-only list tool with an output schema and three optional, fully documented parameters, the description is adequate. It falls short only in not clarifying the default ordering implied by 'top' nor explicitly explaining the search fields (e.g., CIK), but these are minor given the schema and output schema.

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 page, limit, and search are already fully documented. The description merely restates that search and pagination are supported without adding any parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 verb 'List' and the resource 'top institutional investors tracked in the SEC 13F database', which separates it from 'insider traders' or 'stock holders'. However, it does not explicitly contrast with sibling tools like list_insider_traders or get_institution_holdings, so it stops short of full differentiation.

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

Usage Guidelines2/5

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

No guidance is given on when to choose this tool over alternatives. The sentence 'Supports search by name and pagination' describes capabilities rather than usage context, and no exclusions or alternative-tool routing is mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.