Skip to main content
Glama

Arkanum Data: SEC insider trades

A fund's holdings

fund_holdings
Read-only

A tracked fund's latest 13F: every holding with its value, share of the portfolio and change from the quarter before, plus what it sold out of. Values as reported in the filing. Hobby and Pro.

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": "fund_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesFrom list_funds, e.g. 1067983 (Berkshire Hathaway)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and closed-world scope, so the description's job is lighter. It still adds real value by disclosing data provenance ('as reported in the filing') and plan availability ('Hobby and Pro'), which annotations do not cover. It omits 13F timing lag and behavior when a fund has no filing, keeping it short of a 5.

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, all front-loaded: the payload contents come first, followed by the provenance caveat and availability. Every clause carries information an agent would otherwise have to guess.

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

Completeness5/5

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

With one documented parameter, no output schema and strong read-only annotations, the definition covers what an agent needs: the source of the identifier, the fields returned, and the data caveat. Remaining gaps (13F filing lag, empty-holdings behavior) are minor for a single-arg read tool.

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% for the single parameter, and the schema description already supplies the source (list_funds) and a concrete example (1067983). The prose adds no further meaning about cik, so the baseline of 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?

The description names a specific verb+resource ('latest 13F' holdings) and enumerates exactly what comes back: value, share of portfolio, quarter-over-quarter change, and sold-out positions. It implicitly separates itself from the insider-oriented siblings, but never explicitly contrasts with get_filing, which could also surface 13F data.

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?

Usage is only implied: an agent must infer that this is the tool for portfolio composition once it has a CIK. The schema does route the agent to list_funds for the CIK, which provides a workflow hint, but there is no explicit when-to-use or when-not-to-use guidance in the description itself.

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