Signal8

Get Institution Holdings

get_institution_holdings

Read-only

Get the full portfolio holdings for a specific institution by CIK. Returns all positions from their latest 13F filing with shares, value, and portfolio weight. Supports pagination for institutions with large portfolios.

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_holdings"
  }
}

Input Schema

Name	Required	Description
`cik`	Yes	SEC CIK number of the institution
`limit`	No	Maximum results to return (default: 20, max: 100)
`offset`	No	Offset for pagination (default: 0)

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJun 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / cik / description
```
Added value: +"SEC CIK number of the institution"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results to return (default: 20, max: 100)"
```
- addedInput schema / properties / offset / description
```
Added value: +"Offset for pagination (default: 0)"
```
- removedOutput schema / required
```
Removed value: -[
-  "data"
-]
```

Changed1 schema field changedJun 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {}
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedJun 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data originates from the latest 13F filing (implying quarterly, filing-lagged data) and that large portfolios are paginated. It omits edge-case behavior such as what happens when an institution has no 13F on file, which keeps it at 4.

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 short sentences, each earning its place: purpose and key first, then return payload, then pagination caveat. Front-loaded with the verb+resource and no filler or repetition of the title.

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 three-parameter read tool with full schema coverage, annotations, and an output schema, the description covers what the tool returns and how it scales. The only meaningful gap is failure/empty-result behavior when an institution has no 13F holding on record, which an agent calling with an arbitrary CIK would benefit from knowing.

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% and all three parameters (cik, limit, offset) are documented in the schema with defaults and bounds. The description only restates CIK as the lookup key and mentions pagination generically, adding no syntax or format meaning beyond the schema. 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 and resource ("Get the full portfolio holdings for a specific institution by CIK") and pins the data source ("latest 13F filing") with the fields returned (shares, value, portfolio weight). It does not explicitly distinguish itself from close siblings like get_institution_position_changes, get_institution_derivatives, or get_institution_portfolio_analytics, so it stops short of a 5.

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 a specific institution by CIK" implies the use case (point-in-time holdings for one known institution), and pagination is mentioned. However, with four or more institution-focused siblings in the toolset, the description offers no explicit when-to-use/when-not or alternative routing, leaving the agent to infer the boundary.

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

All Signal8 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.