Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

sec_13f_institutional_whale_insider_tracker

Read-onlyIdempotent

SEC 13F Institutional Whale & Insider Tracker: Extracts SEC Form 13F institutional holdings and Form 4 insider trading disclosures.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sec_13f_institutional_whale_insider_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum SEC filing records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum SEC filing records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether 13F and Form 4 results are returned together or how they are distinguished, what time window of filings is covered, or how fresh the data is, despite openWorldHint implying an external live source.

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 no filler; the name-plus-purpose structure is efficient. The repeated product name before the colon is mildly redundant with the tool name but costs little.

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 low-complexity tool with one optional parameter and no output schema, the definition states the source forms and the resource clearly enough to call. It falls short on how the two form types are combined or filtered in the response, which an agent would need to interpret results.

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?

With one optional parameter at 100% schema description coverage, the schema fully documents maxResults, so the baseline of 3 applies. The description adds no meaning about how the limit interacts with the two filing types or what ordering the limit applies to.

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?

Names a specific verb (Extracts) and two concrete resources (SEC Form 13F institutional holdings and Form 4 insider trading disclosures), so the agent knows exactly what data domain this covers. It does not, however, differentiate itself from the sibling sec_edgar_filings, which an agent might reasonably consider interchangeable.

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?

The description gives no when-to-use guidance, no exclusions, and no mention of when to prefer it over the generic sec_edgar_filings sibling. The agent must infer the selection criteria from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources