TradeStar Insider
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| insider_buysA | Use when the user asks which insiders bought a stock, whether a ticker has insider buying, or for Form 4 buys in a date range. Pass |
| insider_cluster_buysA | Use when the user asks about cluster buying, multiple insiders buying the same company, or the strongest insider-buying signal. Returns only clusters (>=2 insiders buying one issuer in-window), newest first; |
| federal_awards_recentA | Use when the user asks about recent federal contracts, government awards, or who won a U.S. federal contract. Returns newly signed federal awards, newest first; |
| activist_stakes_recentA | Use when the user asks about activist investors, hedge-fund stakes, or recent 13D filings on a company. Returns activist Schedule 13D/13D-A filings on US-listed companies, newest first then by stated-intent strength; |
| fund_position_changesA | Use when the user asks what a fund bought or sold, how a 13F filer changed its holdings, or which institutions opened/added/trimmed/exited a position. Returns quarter-over-quarter deltas, newest first; |
| verify_insider_purchaseA | Use when the user wants to verify or fact-check a claim that an insider bought a stock, or to pull the purchases in one filing by accession. Pass the claim (ticker/issuer, person, amount, timeframe), or pass |
| verify_activist_13dA | Use when the user wants to verify or fact-check a claim about an activist stake or 13D filing (ticker/subject, filer, percent-of-class, stated intent, timeframe). Returns confirmed (with source filing + link), not_found, partial (itemised claimed-vs-filed), out_of_scope (passive 13G isn't covered), or out_of_coverage. Every response states the coverage window checked. Caveat: filing-verified — absence is reported as absence, never guessed. |
| verify_8k_eventA | Use when the user wants to verify or fact-check that a company filed an 8-K carrying specific SEC item code(s) in a timeframe. Pass registrant (cik/company/accession), item code(s) and dates. Returns confirmed (with source filing + link), not_found, partial (itemised claimed-vs-filed), out_of_scope (claims about the filing's meaning aren't covered — it is never paraphrased), or out_of_coverage. Caveat: filing-verified — item codes are the SEC controlled vocabulary parsed from the filing, never inferred. |
| verify_13f_changeA | Use when the user wants to verify or fact-check whether a fund (filer name/CIK) reported a CHANGE in a position in an issuer (issuer_name or cusip) in a quarter. Returns held (reported a change — opened/added/trimmed, with source filing + link), not_held (reported the position exited), not_found (no reported change — does NOT mean the fund didn't hold it), or out_of_coverage. Caveat: filing-verified; CANNOT confirm an unchanged holding (13F deltas only) — a 'held, unchanged' position produces no row. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The retrieval tools target distinct filing types (insider buys, clusters, federal awards, 13D stakes, 13F changes) and the four verify_* tools each have a clearly different subject. The main risk is overlap between insider_buys and insider_cluster_buys (cluster is a subset of buys) and between fund_position_changes and verify_13f_change, but the descriptions draw the boundaries explicitly.
All names are snake_case and the verify_ prefix forms a clean, predictable pattern across the four verification tools. The retrieval tools are slightly less uniform (insider_buys vs federal_awards_recent vs fund_position_changes) but remain readable and coherent as a topic-based group.
Nine tools is well within the ideal 3-15 range, and each earns its place: five discovery tools for distinct filing types plus four matching verifiers. No redundant or filler tools.
The surface covers discovery and verification across insider, activist, 13F, and 8-K domains, which is strong lifecycle coverage for a filing-intelligence server. Minor gaps: 8-K has verification but no discovery counterpart, and there is no sell-side/13G or general filing-search operation, though agents can work around these.