Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Find 13F Manager by Name

thirteenf_search_managers
Read-onlyIdempotent

Find a 13F manager's CIK by name — substring / case-insensitive full-text search over filer names. Use this FIRST when you know a manager by name but not their CIK, then pass the resolved CIK to thirteenf_portfolio, thirteenf_overlap, thirteenf_screen, or search_activist_positions. Fixes the 'exact registered legal name required' problem.

Returns candidate managers (cik, filer_name, tier, is_notable, manager_type, manager_styles, current_total_value), notable + largest first. A query can match several entities (e.g. 'berkshire' → Berkshire Hathaway Inc AND Berkshire Asset Management) — pick the right CIK from the candidates.

Examples: 'berkshire' → Berkshire Hathaway Inc (cik 1067983); 'baupost' → BAUPOST GROUP LLC/MA; 'tiger global' → TIGER GLOBAL MANAGEMENT LLC. Note: only managers that file 13F are covered; a name with no 13F filings returns no hits even if it's a known fund. Each candidate carries accession + filing_url (its 13F for latest_report_date; open with get_filing) and accessions (every 13F/amendment that quarter).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name_query": "<name_query>"
    },
    "name": "thirteenf_search_managers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax candidates to return (default: 20, max: 50)
name_queryYesManager name or substring (case-insensitive), e.g. 'pershing', 'third point', 'icahn'.
is_notable_onlyNoIf true, return only notable (smart-money) managers. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds substantial detail beyond them: result ordering (notable then largest first), the fact that a query can legitimately match multiple distinct entities, the returned field list, and the accession/filing_url fields with a pointer to get_filing for opening them. The 13F-only coverage caveat is a genuine behavioral limit an agent would otherwise learn only by getting empty results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence front-loads purpose and the call-to-action ordering, and the multi-match warning is well placed. It runs somewhat long, with both field lists and parenthetical examples partly redundant, but nearly every sentence carries actionable information.

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?

With no output schema, the description compensates by enumerating returned fields (cik, filer_name, tier, is_notable, manager_type, manager_styles, current_total_value) and the embedded accession/filing_url data. Combined with the disambiguation guidance for ambiguous names, an agent has everything needed to call it and interpret results.

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 name_query, limit, and is_notable_only are already documented; the description only reinforces matching semantics for name_query and hints at ordering. It says nothing about limit or about how is_notable_only interacts with the stated 'notable + largest first' ordering, so it does not add meaning beyond the schema.

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 (find a 13F manager's CIK) and immediately qualifies the matching mode (substring, case-insensitive full-text over filer names). It also frames what the tool is not: it is a resolver, distinct from downstream tools like thirteenf_portfolio and thirteenf_overlap that consume the CIK.

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

Usage Guidelines5/5

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

Explicitly says to use this FIRST when you know a name but not a CIK, names the four sibling tools to pass the result to, and gives a concrete exclusion (only 13F filers are covered; a known fund with no 13F filings returns no hits). The 'exact registered legal name required' pain point is called out, which tells the agent why this tool exists.

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.

Resources