Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_sec_institutional_positions_search

Search SEC 13F institutional positions by manager CIK for exact portfolios or by issuer name/CUSIP for best-effort holdings.

Instructions

Search the SEC institutional positions dataset. Searches institutional investment managers' quarterly 13F portfolio holdings stored in a search index. Filter by manager_cik for a manager's full reported portfolio (an exact, reliable filter), or by issuer_name/cusip for a best-effort view of which managers reported a position in an issuer — SEC publishes no authoritative CUSIP-to-CIK mapping, so the issuer side is never a guaranteed-resolved join. Sort enum: value_desc, value_asc, shares_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, defaults to 1
sortNoSort enum: value_desc, value_asc, shares_desc
cusipNoExact CUSIP filter, max 16 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
issuer_nameNoIssuer-name text filter (best-effort match, not a resolved CIK join), max 256 characters
manager_cikNoExact institutional-manager CIK filter, numeric or zero-padded

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "value_desc",
+  "value_asc",
+  "shares_desc"
+]
  2. Added
  3. Removedv1.6.0
  4. Addedv1.6.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden, and it delivers by disclosing a key data-quality trait: SEC publishes no authoritative CUSIP-to-CIK mapping, so issuer-side results are never a guaranteed-resolved join. It also frames manager_cik as reliable and issuer filters as best-effort. It does not mention rate limits or result structure, but the core behavioral caveat is well covered.

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?

Three dense sentences, each earning its place: dataset identification, filter semantics with caveats, and sort options. The most important scoping and reliability information is front-loaded, with no filler or restatement of the name.

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?

Given the tool's moderate complexity (6 optional parameters, no output schema), the description covers the dataset, filter reliability, join limitations, and sort options. It does not explicitly state that calling with no filters returns a broad page of results, but pagination defaults are already in the schema, so the description is sufficiently complete for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: manager_cik is 'exact, reliable,' issuer_name/cusip provide a 'best-effort view,' and the sort enum values are restated with a domain context. This elevates it above the baseline.

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 opens with a specific verb and resource: 'Search the SEC institutional positions dataset,' then clarifies the domain: institutional investment managers' quarterly 13F portfolio holdings in a search index. This clearly distinguishes the tool from generic news/search tools and even from related SEC tools by naming the exact dataset and entity type.

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 explicit filter-selection guidance: use manager_cik for an exact, reliable full-portfolio filter, and use issuer_name/cusip for a best-effort issuer view. It does not explicitly name alternative sibling tools or state when to prefer this tool over datasets_sec_institutional_positions_facets or sec_institutional_holdings, so it falls short of a 5.

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

Deploy Server

Other Tools