Signal8

Get Institution Derivatives

get_institution_derivatives

Read-only

Get an institution's reported put/call derivative positions by CIK (13F options), with pagination and sorting.

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

Input Schema

Name	Required	Description
`cik`	Yes	SEC CIK number of the institution
`limit`	No	Maximum results to return (default: 20)
`offset`	No	Offset for pagination (default: 0)
`period`	No	Filing period to filter (e.g., "2025-Q1")
`sortBy`	No	Column to sort by
`sortOrder`	No	Sort direction

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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)"
```
- addedInput schema / properties / offset / description
```
Added value: +"Offset for pagination (default: 0)"
```
- addedInput schema / properties / period / description
```
Added value: +"Filing period to filter (e.g., \"2025-Q1\")"
```
- addedInput schema / properties / sortBy / description
```
Added value: +"Column to sort by"
```
- addedInput schema / properties / sortOrder / description
```
Added value: +"Sort direction"
```
- 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

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 the safety profile is covered elsewhere. The description adds that results come from 13F option reporting and are paginated/sortable, which is modest but real context beyond the annotations. It does not say whether missing periods return empty, how current the filings are, or what a position record contains.

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?

A single front-loaded sentence with the verb, resource, lookup key, and capability set, plus a compact parenthetical for the data domain. There is no filler and nothing an agent must read past to find the core action.

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 simple read-only lookup with six fully documented parameters and an output schema that covers return values, the description supplies what an agent needs to decide and call. The remaining gap is the absence of routing guidance against the many institution siblings, which is a discoverability concern rather than a missing call detail.

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 coverage is 100%, so every parameter including cik, limit, offset, period, sortBy, and sortOrder is already documented in the schema. The description only restates that pagination and sorting exist, and 'by CIK (13F options)' adds the source context but no format or default details beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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?

The description names a specific verb and resource ('Get an institution's reported put/call derivative positions by CIK') and adds the data source qualifier '(13F options)', which distinguishes it from the broader holdings/portfolio siblings. It does not explicitly name a sibling tool, 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 Guidelines2/5

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

Use is only implied by the resource name; there is no statement of when to prefer this over get_institution_holdings, get_institution_portfolio_analytics, or get_institution_position_changes. No exclusions, prerequisites, or fallback guidance are given.

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.