Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Institution Filings

get_institution_filings
Read-only

Retrieve an institution's 13F filings by SEC CIK with pagination controls to browse filing history and results.

Instructions

Get the list of 13F filings for an institution by CIK, with pagination.

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": {
      "cik": "<cik>"
    },
    "name": "get_institution_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesSEC CIK number of the institution
limitNoMaximum results to return (default: 20, max: 50)
offsetNoOffset for pagination (default: 0)

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, destructiveHint=false and openWorldHint=false, so safety and scope are covered structurally. The description adds only that results are paginated, which is already implied by the limit/offset schema, and says nothing about ordering, coverage period, or empty-result behavior.

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?

A single front-loaded sentence with zero filler, correctly leading with the resource and scope. It is efficient, though its brevity comes at the cost of any routing or behavioral detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and all three parameters are documented in the schema. What is missing is any differentiation from the dense cluster of institution and filing siblings, which is the main thing an agent needs in order to select this tool correctly.

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%, with cik, limit (max 50, default 20) and offset all documented in the schema itself. The description merely restates the CIK scoping and mentions pagination, adding no format or semantics beyond the structured fields; baseline 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?

States a specific verb (get) and resource (13F filings) scoped to an institution identified by CIK. It is distinguishable from holdings-oriented siblings like get_institution_holdings, but it never names an alternative or clarifies the boundary with filing-search tools such as search_sec_filings or get_filing_calendar.

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

Usage Guidelines3/5

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

The phrase 'for an institution by CIK' implies the usage context of looking up a known institution's filing history. However, there is no explicit when-to-use guidance, no exclusions, and no pointer to the several sibling tools that also surface filings.

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