Skip to main content
Glama

Arkanum Data: SEC insider trades

Bulk file download links

bulk_file_links
Read-only

Download links (valid one hour) for yearly files of every open-market insider buy and sale, gzipped CSV and Parquet. Hobby: 2023 on; Pro: 2006 on.

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

Input Schema

NameRequiredDescriptionDefault
yearNoOne year only, e.g. 2025
formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, closed-world safety profile, and the description adds genuinely new behavioral facts: links expire after one hour and files are gzipped CSV/Parquet. It stops short of saying whether links are per-year or batched, or what the response object looks like.

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?

Two tight sentences; the core capability is front-loaded and the plan-tier constraint follows. No filler wording to trim.

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?

For a no-output-schema, 2-param export tool, the description covers format, expiry, and tier coverage well. It leaves the optional-`year` behavior and the shape of the returned links undocumented, which an agent needs to invoke it 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 coverage is 50%: `year` is self-documented and `format` is a self-explanatory enum. The description reinforces that files are yearly and that both csv.gz and parquet exist, but it never explains what happens when `year` is omitted despite zero required parameters, which is the main semantic gap.

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+resource: it returns download links for yearly bulk files of open-market insider buys and sells. Sibling tools are all query/lookup style, so the bulk-export nature is implicitly distinct, but the description never names an alternative to route against.

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?

Plan-tier coverage ("Hobby: 2023 on; Pro: 2006 on") tells the agent which years are reachable, which is real usage context. It never says when to pick this over search_insider_trades or search_insider_history, so the choice between bulk export and filtered query is left to inference.

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