Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_sec_institutional_positions_search

Search the SEC institutional positions dataset. Searches institutional investment managers' quarterly 13F portfolio holdings stored in a search index.

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the billing model (1 credit per record, minimum 2, 100 for a full page) and the reliability caveat of the issuer-side join. It omits auth/permission needs and any pagination limits beyond what the schema states.

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?

Front-loaded with the purpose, then filters, sort, and billing in order of importance; every clause is informative. The em-dash asides add slight length but no filler.

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 search tool with no output schema and no annotations, the description covers data source, filter semantics, sort, and cost. It does not describe the shape or fields of returned records, which is the main remaining gap.

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 genuine meaning by characterizing manager_cik as exact/reliable and issuer_name/cusip as never-guaranteed joins, which an agent cannot infer from the schema descriptions alone.

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 (Search) and resource (SEC institutional positions dataset / quarterly 13F holdings), which clearly distinguishes it from siblings like datasets_sec_companies_search or datasets_sec_institutional_positions_facets. An agent knows exactly what data this touches.

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?

Explains the two filter modes clearly: manager_cik for a full reliable portfolio view vs issuer_name/cusip for best-effort issuer lookups, including the reason the issuer side is unreliable. It does not reference sibling tools (e.g. facets) as alternatives, so it stops short of full when/when-not routing.

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